Interfaces
Connect MCP
MCP (Model Context Protocol) lets an agent use tools that live outside Wrenchit. You can connect remote MCP servers to WCode today. A Wrenchit-hosted MCP server at mcp.wrenchit.net is planned, not live.
Status: hosted endpoint not available. mcp.wrenchit.net is reserved as the public address for the Wrenchit MCP server. It does not serve an MCP endpoint yet. Connecting to it will fail. Use the WCode connector described below to add servers you run or subscribe to.
Status
| Surface | Status | What it means |
|---|---|---|
| MCP client in WCode | Available | Add a remote server by URL in Connectors, authenticate, and use its tools in a session. |
Hosted server at mcp.wrenchit.net | Planned | No endpoint, tools or registry are served there yet. Do not point a client at it. |
| Wrenchit tool catalog | Planned | Wrenchit's own tools are not yet published over MCP. |
What MCP is
A plain API gives you endpoints you call from code. MCP gives an agent a list of tools it can discover and call while it works: search a knowledge base, read a ticket, query a database, post a message. The server describes its tools; the client (WCode) exposes them to the model; you decide what the agent may use.
Two terms are worth keeping straight:
- Server. The thing that owns the tools and the data behind them. It can be remote (a URL) or local to your machine.
- Client. WCode. It connects to servers, lists their tools, and routes the model's tool calls to the right one.
Connect a server
-
Open Connectors
In ai.wrenchit.net, open Connectors and choose MCP servers. The page lists the servers you have added and their connection state.
-
Pick a server or add a URL
Choose one from the catalog, or add any remote server by its URL. Use the server's MCP endpoint, not its documentation page. A URL that returns HTML in a browser is usually not an MCP endpoint.
-
Authenticate
If the server uses OAuth, choose Add and sign in and complete the flow in the browser. If it issues a token, paste the token when prompted. Tokens are kept in the encrypted credential store and sent as a bearer token, never written to config.
-
Check the tools
Open the server's tool list. A connected server with no tools is usually a permissions problem on the server side, not a Wrenchit problem. Reconnect after fixing it.
-
Use it in a session
Start or open a session. The agent can call the server's tools when the task calls for them. Ask for the tool by name if the agent does not pick it up on its own.
Managing a connection
- Reconnect renews an expired token or re-runs the OAuth flow.
- Remove deletes the entry and its stored sign-in. Agents lose the tools from that server immediately.
- Status reads Connected, Connecting, Off, Failed, Needs sign-in or Needs client ID.
Tools and permissions
Each server advertises its own tools; Wrenchit does not rename them. Tools appear to agents as name_tool, using the server name you gave it.
Every agent can use the tools you add. Tools that only read run on their own; anything that may change something asks you first. If a tool is missing, check the server's own permissions first, then reconnect.
A connected server can see what you send it. Tool arguments leave Wrenchit and go to the server's operator. Connect servers you trust with the data in that project, and remove connections you no longer use.
The hosted endpoint
mcp.wrenchit.net is the address reserved for Wrenchit's own MCP server. When it ships, it will publish Wrenchit tools over MCP so an external client can use them without a WCode session.
Until then:
- There is no endpoint to connect to, and no tools to list.
- There is no API key or token to request for it.
- Any page or post claiming a live Wrenchit MCP endpoint is ahead of the product.
The current status is kept on the stub page at mcp.wrenchit.net. For the client side, see Install WCode.