Connect your agent

https://conecto.chat/SKILL.md is the file an agent keeps. It says how to sign up, call tools, pay and keep the business safe, then lists every area with its prices and tools. An agent that reads it signs itself up with one call.

Set up Conecto from https://conecto.chat/SKILL.md

Agents that look for skills on their own find it at https://conecto.chat/.well-known/agent-skills/index.json. For agents lists its sections and its digest. A Conecto partner's link adds ?ref=<code> to the address, and the file then puts their code in its signup example.

One MCP server holds every area a key may use, https://api.conecto.chat/v1/mcp, over Streamable HTTP. Calling a tool needs the key in the Authorization header. An agent adds it once, right after signing up, with the key typed in that one command:

claude mcp add --transport http --scope user conecto https://api.conecto.chat/v1/mcp \
  --header "Authorization: Bearer $CONECTO_KEY"

Each area also has a server of its own at https://api.conecto.chat/mcp/<area>, for an agent that wants only some areas. Listing its tools needs no key, and it carries the account tools too, like account_balance.

A key limited to some areas or tools sees only those in tools/list. Calling tools shows a call and its reply over MCP.

Assistants that people use, like ChatGPT, Claude and Grok, and agents built in Copilot Studio, sign in with OAuth at one address for every area, https://api.conecto.chat/v1/mcp. Add it as a custom connector (in Copilot Studio, a Model Context Protocol tool), sign in to Conecto, tick the areas the app may use and allow it.

• The owner signs in with the session they have on conecto.chat. Anyone else on the account signs in with a link emailed to them, or through the company's single sign-on.
• They pick the account and tick the areas. The business's areas are ticked already, and Select all ticks every one. The connection then runs on a key of its own, limited to those areas, so it shows with the account's other keys and is revoked like them.
• Tools that move money, like topping up, stay out of the connector whatever is ticked.
• A token works only on the connector's address. An access token lasts 1 hour, and a refresh token 30 days.
• Someone on the account besides the owner connects as themselves. The key is theirs, named like "Ben, through Claude", and works within their teams and role. Removing them from the account ends it at once.
• The owner can list the apps people may connect. An app that signs people in from anywhere else is refused.

The sign-in follows OAuth 2.1 with PKCE, dynamic client registration and resource indicators, and refresh tokens change with each use. The connector's metadata is at https://api.conecto.chat/.well-known/oauth-protected-resource/v1/mcp, and For agents shows it.

Any code that speaks HTTPS calls POST https://api.conecto.chat/v1/tools/<name>. These OpenAPI files describe it:

An area's file also carries the account tools. In the file for a custom GPT, a tool that only reads is marked so ChatGPT can offer to always allow it. The REST API has every route.

Each page gives the steps from that agent's own docs, with the addresses to paste.

• Claude: Custom connector.
• ChatGPT: Custom MCP server.
• Grok: Custom connector.
• Claude Code: SKILL.md and a setup line.
• Cursor: mcp.json.
• Codex: SKILL.md and a setup line.
• Gemini CLI: settings.json.
• OpenClaw: SKILL.md and a setup line.
• Hermes Agent: SKILL.md and a setup line.

Add the areas the business uses. Each link opens the area's tools.

Assistants that sign in use one connector for every area: https://api.conecto.chat/v1/mcp. Agents with a key use each area's MCP server.

Every server's address starts with https://api.conecto.chat.