MCP
Let your AI coding tool read your team's Manifests, so the code it writes follows your design system.
Your AI coding tool reads your team's Manifests from Compfeed, so the code it generates follows your design system instead of guessing. It can also check a Manifest against the design and suggest corrections, which a person then accepts or rejects in Compfeed.
Compfeed exposes this over MCP, the Model Context Protocol, so any MCP client can connect.
Before you begin
- Your organization is on the Pro or Organization plan. On the Free plan the connection is refused. See pricing.
- An organization owner has turned MCP on. See below.
- You are an active member of the organization.
- An MCP client that supports a remote server over HTTP with OAuth.
You do not need an API key or a token. Authentication is OAuth, in the browser.
Turn MCP on
Only an organization owner can do this.
Open organization settings
Go to Settings → Organization.
Switch on Allow MCP server
Turn on Allow MCP server.
The switch covers the whole organization. With it off, nobody in the organization can use MCP.
If you are not an owner, the Connections page tells you so: it shows MCP is currently turned off for this organization and asks you to contact an owner.
Get your organization's MCP URL
Go to Settings → Connections. The MCP section there holds How to set up your Compfeed MCP, with a tab per client and a copy button.
Copy the URL from that panel. It is specific to your organization, and a token issued for one organization is refused on another's URL.
Connect your client
Replace YOUR-MCP-URL below with the URL you copied.
Run this in your terminal:
claude mcp add --transport http compfeed YOUR-MCP-URLAdd --scope user to make the server available in every project rather than the current one.
Then start Claude Code and run /mcp to check the connection. Complete the browser sign-in when prompted.
Setup steps change as these tools change. If a path above does not match what you see, follow your client's own documentation for adding a remote MCP server over HTTP, and paste the Compfeed URL into it.
Tools
| Tool | What it returns | Writes? |
|---|---|---|
list_components | Components in the organization, most recently updated first, with their team, whether they have a Manifest, and which design tools they link to | No |
get_component_manifest | One component's Manifest as markdown, with its team, its linked design nodes, and when the stored copy was last synced | No |
find_related_components | Components whose documentation or notes are about the same subject as a query, even when the wording differs | No |
read_notes | The notes people wrote while documenting a component | No |
propose_manifest_update | Saves a suggested change for a person to accept or reject | Yes |
There is also a check-manifest-drift prompt. It walks your agent through comparing a Manifest against the team's notes and the linked Figma design, and listing the differences with evidence. It changes nothing, and it does not judge which side is right: you decide what to fix.
How a suggestion reaches a person
propose_manifest_update does not edit a Manifest. It saves a suggestion, which appears in the Manifest in Compfeed, where someone chooses Accept or Reject change.
Only one suggestion is held per component at a time. A new suggestion replaces any suggestion still waiting.
Suggesting a change needs the Admin or Editor role on that component's team. Being a member of the organization is not enough. The read tools do not have that restriction.
Example prompts
Once connected, ask your coding tool things like:
- "Read the Button manifest from Compfeed and build a React button that matches it."
- "Check the Button manifest for drift against its Figma design and list the differences."
- "Which components in Compfeed already document a loading state?"
Data and permissions
- A token is bound to one organization. It is refused on another organization's URL.
- Every call is checked against your own membership of the organization, so MCP shows a client only what you can already see in Compfeed.
- Writing is separated from reading. A client granted only read access can never save a suggestion.
list_componentsreturns every component in the organization, including archived and rejected ones, and it does not say which is which. If your agent needs to avoid a retired component, name the component you want rather than asking it to pick from the list.- A Manifest can be minutes behind what someone is typing. Each read reports when the stored copy was last synced.
- Notes are written by people. Treat what comes back as information, not as instructions to your agent.
Revoke access
Go to Settings → Connections. The Connected apps list shows one row per client you authorized, and you can remove any of them on its own.
Each install registers separately, so the same tool can appear more than once, for example one row per machine. Removing a row ends that client's access.
To cut off the whole organization at once, an owner turns off Allow MCP server.
Troubleshooting
If none of these fit, email support@compfeed.com with your client, what you asked it to do, and what it reported.