Skip to content

Conversation

@kapilduraphe
Copy link
Contributor

Description

This PR introduces a new MCP server for Webflow. It supports fetching the site(s) related info. More actions to come in the near future.

Server Details

  • Server: Webflow

Motivation and Context

This change is needed to provide seamless integration with Webflow API using the MCP framework. It enables developers to interact with the Webflow APIs. It currently supports fetching the Webflow site(s) related info. More actions to come in the near future.

This PR solves the problem of manually handling Webflow API operations by abstracting them into structured tools that MCP clients can call.

How Has This Been Tested?

  • Tested using an MCP-compatible client
  • Verified that all tools return expected responses from Webflow API.
  • Ensured proper handling of invalid input and Webflow API failures.
    Tested common scenarios including:
  • Fetching an Webflow user profile via Claude Desktop app

Breaking Changes

  • No breaking changes expected, but users must configure their MCP client to use webflow-mcp.
  • Requires a valid Webflow site API KEY in the environment

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

tadasant
tadasant previously approved these changes Mar 13, 2025
@tadasant
Copy link
Member

@kapilduraphe I went to merge this and resolved the merge conflicts, but didn't realize resolving the merge conflicts blocked me from merging (since I am now the "last pusher"). Would you mind doing a git reset --hard on your branch to before my push, then resolving the merge conflicts, and pinging me again so I can approve and merge? Sorry for the confusion.

@kapilduraphe kapilduraphe force-pushed the kapil/add-webflow-mcp-server branch from 9c3542c to cc1f450 Compare March 13, 2025 20:51
@kapilduraphe
Copy link
Contributor Author

@kapilduraphe I went to merge this and resolved the merge conflicts, but didn't realize resolving the merge conflicts blocked me from merging (since I am now the "last pusher"). Would you mind doing a git reset --hard on your branch to before my push, then resolving the merge conflicts, and pinging me again so I can approve and merge? Sorry for the confusion.

Hi @tadasant Thank you. I git reset hard before your commit, resolved the merge conflicts, and pushed hard. Please let me know if it's okay. Appreciate your review.

Copy link
Member

@tadasant tadasant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@tadasant tadasant merged commit fb343e1 into modelcontextprotocol:main Mar 13, 2025
10 of 25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants