connections

Connections

A connection gives your agent access to one third-party service. Your agent writes it for you.

Anatomy of a connectionconnections/github/
connection.yamlsecret names + deps
index.mdthe API in practice
How the agent uses it
1
Read index.md
Learn the API
2
Call the API
Secrets by name only
3
Return the result
Values injected, output scrubbed

What is a connection

A connection is one folder per service under connections/. connection.yaml declares what the service needs by name: which secrets, which Python packages. index.md holds how the API works in practice.

Secret values never appear in these files. They live in secrets.env, gitignored, injected at run time and scrubbed from every output.

connections/github/connection.yaml
name: github
description: GitHub REST API - repos, issues, pull requests
kind: source-control
secrets:
- GITHUB_TOKEN
deps:
- requests

How to add a connection

Run the setup prompt in your client and name the service. The agent writes the folder, asks you to paste the token into secrets.env, and verifies the connection against the real API.

You paste one value into one file. Everything else is the agent's work.

in your client
$ /mcp__my_instance__setup
> Connect to GitHub.
Creating connections/github/
connection.yaml secrets: GITHUB_TOKEN, deps: requests
index.md auth style, endpoints, gotchas
Add the value to secrets.env, then say "done":
GITHUB_TOKEN=ghp_...
> done
Smoke test: GET /user ... 200 OK
Connection ready.
Agents list the connections they need

Now that you know what a connection is, pick an agent. Setup maps its connection slots to your services.

Browse agentsGet started →