Theme
AI tools
Connect a tool
Everything you need is on the AI tools page in Vythos: the server address, a key, and a ready-made snippet per tool. Copy from there rather than from here — the address is shown to you rather than hard-coded, so it's always the right one for your workspace.
Two ways to prove who you are
Claude, ChatGPT and Gemini sign in with your Vythos account (OAuth): no key to paste or keep safe. Everything else uses a key sent as an Authorization: Bearer … header. Either way, the connection carries the access of the person it belongs to.
Claude Desktop
- In Vythos, open AI tools and copy the server address.
- In Claude Desktop: Settings → Connectors → Add → Custom connector.
- Paste the address and choose Connect.
- Your browser opens. Sign in to Vythos and approve. The connection can read your Playbook, search and read your memory and log outcomes, as the approval page lists. It can also propose a rule or a fact when you ask it to, which waits for the workspace owner to add (see Save from your AI tools); it can't change a rule itself.
No key needed. The connection appears on the AI tools page, where you can see when it was last used.
ChatGPT
- In Vythos, open AI tools and copy the server address.
- In ChatGPT: Plugins → Add → Add custom MCP server.
- Name it
Vythos, paste the address, and leave Authentication on OAuth. ChatGPT finds the sign-in settings by itself. - Tick I understand and want to continue, then Create as a plugin.
- Sign in to Vythos and approve, as for Claude above.
In a chat, type @Vythos to use it.
Gemini
Google offers custom connected apps in the Gemini app to people in the US for now, aged 18 or over, with Keep Activity on.
- In Vythos, open AI tools and copy the server address.
- In the Gemini web app, add a custom connected app and paste the address as its MCP server.
- Sign in to Vythos and approve. It then works in the Gemini phone app too.
GitHub Copilot
In VS Code, create or edit .vscode/mcp.json in your project root, then choose Vythos in Copilot's agent mode:
json
{
"servers": {
"vythos": {
"type": "http",
"url": "<server-address>",
"headers": { "Authorization": "Bearer <your-key>" }
}
}
}Claude Code
- In Vythos, AI tools → New key, give it a label such as
Claude Code, and copy both the key and the address. - Run the command shown on the page:
bash
claude mcp add --transport http vythos <server-address> \
--header "Authorization: Bearer <your-key>"Use --transport http. The address ends in /sse for historical reasons, but the server speaks Streamable HTTP — --transport sse fails to connect.
Cursor
Create or edit .cursor/mcp.json in your project root:
json
{
"mcpServers": {
"vythos": {
"url": "<server-address>",
"headers": { "Authorization": "Bearer <your-key>" }
}
}
}Windsurf
Settings → MCP, or edit ~/.codeium/windsurf/mcp_config.json with the same shape as Cursor's config above.
Any other MCP client
Three values, and every MCP client needs them:
| Server URL | From the AI tools page |
| Transport | Streamable HTTP (POST) |
| Auth header | Authorization: Bearer <your-key> |
Most tools that advertise MCP support work with this. The ones listed on the AI tools page are the ones we've connected ourselves.
Teach your AI how to work with Vythos
Every connected tool is told the basics as it connects: load the rules first, check the draft, report back. Some tools act on that more reliably than others. The Vythos skill is a fuller version, and it's optional.
In Claude Code, paste this into a session:
text
Set up https://vythos.tech/skill.mdIt adds the connection without a key and saves the skill. You do the one step it can't: type /mcp, choose vythos and press Authenticate to sign in.
In other agents, the same line sends them to the AI tools page for their setup steps. If they have no skills folder, they still get the basics once connected.
In Claude on the web or desktop, download the skill and upload it under Customize → Skills.
The skill holds instructions only, and no key. You can read it before you use it.
Check it worked
Ask your tool to do something that needs your rules:
"Using Vythos, what are our standard payment terms?"
or, better, a real task:
"Draft a project proposal for Acme for a three-month retainer. Get the rules from Vythos first, and check the draft before you show it to me."
You should see the tool call Vythos, quote figures that match your Playbook, and — on the check — either report nothing found or name the rule a line breaks.
If it doesn't connect
| Symptom | Likely cause |
|---|---|
| The client can't reach the server | Check the address is exactly the one on the AI tools page, including /sse |
| Connects, then every call is rejected | The key is wrong, revoked, or missing its Bearer prefix |
| Claude Code connects then drops | You used --transport sse. Use --transport http |
| Connects but returns nothing useful | Check the access of whoever owns the key. A category set to no access is never sent |
| The address keeps changing | Your workspace is pointed at a temporary development address. The AI tools page says when that's the case — ask us for the permanent one |
Keys and hygiene
A key is shown once, when you create it. Keep it where you keep other secrets, one key per tool, and revoke any you're unsure about — revoking takes effect immediately. See Keys.
