Connect an MCP server to Knit
Knit can extend the AI’s capabilities with tools from Model Context Protocol (MCP) servers. When a server is enabled, its tools are offered to the chat during each turn. Knit connects over Streamable HTTP only — stdio and SSE transports are not supported — so you provide a public HTTP(S) endpoint and, optionally, an Authorization header.
Before you start
- A reachable MCP server that speaks Streamable HTTP, with a public https URL (for example https://mcp.context7.com/mcp).
- An Authorization header value, if the server requires authentication.
- A Knit account, signed in.
Steps
- 1
Open Knit settings → MCP Servers
In Knit, open /app, click the settings gear, and select the "MCP Servers" tab.
- 2
Add the server
Enter the server’s public URL (required), for example https://mcp.context7.com/mcp. Optionally add a label; if you leave it blank, the URL is used. If the server needs authentication, paste the Authorization header value (for example "Bearer xxx") — it is encrypted at rest and never shown again. Save.
- 3
Test the connection
Click Test on the server row. Knit connects and lists the server’s tools, showing "connected · N tools" on success or an error message if it cannot reach the server.
- 4
Enable it for chat
New servers are enabled by default. Use the Enable/Disable toggle to control whether a server’s tools are offered to the chat. Disabled servers are excluded from every turn.
- 5
Use the tools
Open a project and chat. On each turn, Knit gathers the tools from your enabled MCP servers and lets the AI call them while working on your schematic. If a server is unreachable, the chat still works — its tools are simply skipped.
Frequently asked questions
- Which MCP transports does Knit support?
- Streamable HTTP only. Knit does not support stdio or SSE MCP servers. The server must be reachable at a public http(s) endpoint.
- How do I authenticate to a protected MCP server?
- Put the full Authorization header value (for example "Bearer your-token") in the Authorization header field when adding the server. It is encrypted at rest and sent as the Authorization request header. It is never displayed again after saving.
- How do I check that my MCP server works?
- Use the Test button on the server’s row in settings. Knit connects, runs a tool listing, and reports "connected · N tools" or the connection error so you can fix the URL or auth.
- What happens if an MCP server is down?
- Nothing breaks. Knit loads MCP tools per chat turn and fails gracefully: an unreachable or disabled server is skipped, and the chat continues without its tools.