Connect an agent
Give your agent one address and it can search, read and, if you allow it, write across your network:
https://app.inseam.io/mcpinseam speaks MCP, so it works with any agent that can use an MCP server over HTTP. The agent signs you in through your browser and asks which permissions it may have. You choose the network, the permissions and for how long. You can revoke it at any time from your network page.
The Connect page in the app shows the exact steps for your tool and keeps them current. The steps below are the usual ones.
Claude Code
Section titled “Claude Code”claude mcp add --transport http inseam https://app.inseam.io/mcpThen ask Claude anything about your files. The first call opens your browser for the approval.
Claude.ai, ChatGPT, Cursor and other MCP hosts
Section titled “Claude.ai, ChatGPT, Cursor and other MCP hosts”Add a custom connector or MCP server and paste the address https://app.inseam.io/mcp. Where the tool asks for
a configuration file, this is enough:
{ "mcpServers": { "inseam": { "url": "https://app.inseam.io/mcp" } } }No client id or secret is needed: the host registers itself and your browser opens for the approval.
What the approval asks
Section titled “What the approval asks”| permission | lets the agent | default |
|---|---|---|
| search | search your network and see what is in it | on |
| read | read the text and the bytes behind a result | on |
| write | write and delete on the hosts you pick | off |
You also pick which hosts the agent sees (all of them, or a few) and for how long: 7, 30, 90 or 365 days. When the time is up the agent asks again.
Every agent gets its own folder on your pad, agents/{its name}/, that it may always read and write. That is its
memory: notes it keeps between conversations. You can read and search that folder like anything else.
Headless agents and servers
Section titled “Headless agents and servers”An agent without a browser (a script on a server, a scheduled job) uses a device code. It shows you a short code
and a URL; you open https://app.inseam.io/activate, type the code, and see the same approval page. The exact
flow for builders is in the MCP and OAuth reference.
API tokens
Section titled “API tokens”Anything that speaks HTTP but not MCP uses an API token. In the app, open your network and choose Agents and API tokens, then Create token. Pick a name, the permissions and the hosts, and copy the token: it is shown once. Send it as a bearer token:
curl https://app.inseam.io/v1/search \ -H "Authorization: Bearer ias_…" \ -H "Content-Type: application/json" \ -d '{"q": "quarterly report"}'A token has the same permissions model as an agent. The authentication reference has the details.
Revoke an agent
Section titled “Revoke an agent”Open your network page. Every agent and token is listed with what it may do, when it was last used and when it expires. Revoke ends it at once. The agent’s folder on your pad stays, so a new grant to the same agent finds its notes again.