MCP clients
Connect Claude Desktop, Cursor, and other MCP clients to drive Eddytor with tools.
Eddytor exposes an MCP endpoint at ${public_url}/mcp, so MCP-aware clients -
Claude Desktop, Cursor - can query and manage tables through Eddytor's tools.
This is the interface behind the MCP examples throughout these docs.
Add the server
~/Library/Application Support/Claude/claude_desktop_config.json (macOS):
{
"mcpServers": {
"eddytor": { "url": "http://localhost:8080/mcp" }
}
}Settings → MCP Servers:
{
"eddytor": { "url": "http://localhost:8080/mcp" }
}Point the url at your server's public URL + /mcp.
First-use auth
Good to know
/mcp is outside CORS by design (MCP clients
are programmatic, with their own origin / DNS-rebinding protection).What you can do
The MCP tools cover the full table lifecycle - discover, query, create, load,
govern with domains, version/rollback, maintain, retire. Just ask in natural
language, e.g. "Show the history of eddytor.sales.orders and roll back to
version 40." Permissions still apply: an MCP session can only do what the
authenticated user's role (∩ any scope) allows.
When to use MCP vs the rest
- MCP - LLM/agent-driven work and exploration.
- CLI - scripting and CI.
- REST - app integration.
- Flight SQL - bulk reads.