Custom Connector
If the tool you want is not in the catalog, you can connect it yourself. SetForth talks to integrations over the Model Context Protocol, so anything that exposes an MCP server works the same way the listed tools do, including a server you wrote.
What you need
- A server URL. The address of the MCP server, over HTTPS. SetForth uses Streamable HTTP.
- A way to authenticate. Most servers want a token. Some sign you in through your browser instead.
- A category. This is the important one. See below.
Pick the right category
A category is not a label. It decides which follow-up checks the connection grants, so choosing it wrongly gives agents checks the tool cannot answer.
| Category | Choose it when the tool reports | Follow-ups you get |
|---|---|---|
| Error monitoring | Exceptions and error rates | Reduce error rate, No new errors, No regression |
| Product analytics | Events, funnels, and usage | Verify event tracking, Measure feature adoption, No metric regression |
| Observability | Latency, throughput, and monitors | Hold latency budget, No new alerts |
| Deploys and infrastructure | Releases and service health | Verify deploy health |
Two tools in the same category both work. The follow-ups appear once for each, named after the tool, so you can tell them apart when you plan a task.
Connect it
- In SetForth, open your project, then Integrations.
- Choose Custom MCP server.
- Give it a name. This is what you will see during planning.
- Enter the server URL and pick the category.
- Choose how it authenticates: - Access token for a server that wants
Authorization: Bearer <token>. - Custom header for a server that wants its own header name. - Multiple headers for a server that splits credentials across two or more headers. - Browser sign-in for a server that uses OAuth. SetForth registers itself with the server and sends you there to approve the access. - None for a server that needs no credential. - Choose Connect. SetForth opens the connection, lists the tools the server offers, and tells you if it did not work.
What agents can do with it
Everything the server offers, until you say otherwise. Tool access on the integration's page decides that, for that project: leave it on All tools, or narrow it to Read-only tools so agents can only call the tools the server marks as read only, or pick the exact tools yourself.
Credentials never reach an agent. SetForth calls the server itself and passes back only the result, so a task's sandbox never holds your token.
If the connection fails
- We could not reach that endpoint. The URL is wrong, the server is not running, or it is not reachable from the internet. SetForth calls it from our infrastructure, so a server on your laptop or inside a private network will not work.
- The credentials were rejected. The token is wrong, expired, or lacks permission. Replace it with Update Credentials.
- The connection timed out. The server accepted the connection but did not answer in time.
For a server that signs you in through the browser, the connection carries the access of whoever authorized it. Its page shows who that was, and Reconnect hands it to someone else.