Use eesel from Claude and other AI assistants
Add your eesel workspace to claude.ai, Claude Code, Cursor or any MCP client, and talk to your agent, check on it and change its setup with your dashboard permissions.
Your eesel workspace is an MCP server. Any assistant that speaks MCP can talk to your agent, check on it and change its setup, with the same permissions you have in the dashboard.
claude.ai (Claude chat, desktop and Cowork)
In Claude, open Settings > Connectors and choose Add custom connector.
Name it eesel and enter the server URL:
https://oracle.eesel.app/mcpClaude opens eesel's sign-in page. Sign in and approve. That's the only step, and it's once.
From then on, in any Claude conversation with the eesel connector on, you can say "ask eesel what it did today", "have eesel draft a reply to the refund ticket", "turn on the Slack automation". Claude calls your agent; the reply is your agent's, with its instructions and knowledge.
What Claude gets is a small set of tools named like the CLI's commands: chat (talk to the agent; anything not covered below is something you ask for here), status, integrations, automations, instructions, files, activity, invite, billing. Editors can change things; viewers get the read side. Anything set to need approval still asks, and shows up in your dashboard as usual.
The connector talks to your workspace's first agent (the oldest one that isn't a supervisor). With several agents, say which one you mean in the message, or use the CLI or Claude Code where the agent is a header.
Claude Code, Cursor, Codex and other coding agents
For setting eesel up from a repo or a terminal: Set up from Claude Code or the terminal. For adding your workspace as an MCP server to Claude Code with a token instead of OAuth: Claude Code & MCP clients.
Any other MCP client
Two ways in, pick whichever your client supports:
OAuth: server URL
https://oracle.eesel.app/mcp. The client discovers eesel's authorization server from the standard/.well-knownmetadata and opens the sign-in page.A token: run
npx @eesel/cli mcp tokenand use what it prints: the same URL, anAuthorization: Bearer <token>header, and anX-Eesel-Agent-Idheader naming the agent. Tokens last 30 days and carry your role at the time they were minted.
Any AI agent, with no integration at all
An agent that can browse or run commands needs two things to use eesel well:
https://www.eesel.ai/llms.txt, what eesel is and when to use it, in one file.
https://www.eesel.ai/agent.txt, how an agent should set eesel up and call it, including the CLI commands and the rule that authentication always goes through the person's own login.
Every docs page here is also available as markdown by adding .md to its URL, and the whole set is at https://docs.eesel.ai/llms.txt.
Related
Last updated