The first business OS with a public Model Context Protocol server. Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, ChatGPT — any MCP client. Workspace-scoped keys, read-only mode, feature filtering.
The Workestra MCP server ships as a single npm package. Pass your workspace-scoped API key. That's the entire setup.
--read-only for analytics use.--features=crm,projects.npx -y @workestra/mcp --api-key=sk_live_your_key_here{
"mcpServers": {
"workestra": {
"command": "npx",
"args": [
"-y",
"@workestra/mcp",
"--api-key=sk_live_your_key_here"
]
}
}
}Anthropic's protocol is a 2025 open standard. Workestra is built to it directly — no custom adapters per IDE, no broken parity.
Anthropic's official desktop app — first-class MCP support.
Anthropic's CLI / VS Code agent. Same config file format.
Configure once in Cursor settings, use from any project.
Codeium's agentic IDE. MCP-first.
Via the MCP extension or GitHub Copilot's agent mode.
MCP support for ChatGPT desktop and the OpenAI agents SDK.
Open-source coding assistant — wire Workestra into the workflow.
If it speaks the Model Context Protocol, it speaks Workestra.
Every tool returns a result row that links back to the entity. Every write is in your audit log. Every key is workspace-scoped.
search_contacts · create_deal · update_deal_stage · log_call · send_sms
search_tickets · triage_ticket · draft_reply · merge_tickets · breach_check
log_time_entry · start_timer · create_task · move_to_cycle · approve_timesheet
create_quotation · convert_to_invoice · send_peppol_invoice · record_expense
create_booking_link · check_availability · reschedule · cancel_booking
search_docs · summarise_document · cite_source · suggest_articles
Workspace isolation is enforced at the database row level via Postgres RLS, not just the API. Same defenses your in-app users get.
Keys are issued per workspace. A key for Workspace A cannot read or write any data in Workspace B — enforced at the database row level, not just the application.
We never store the raw key. Only its SHA-256 hash. Lost a key? Revoke and re-issue — no support ticket required.
Pass --read-only to the MCP server (or set it on the API key) and writes are refused at the protocol layer. Safe for analytics and dashboards.
--features=crm,projects exposes only those tool categories. Lock down what an AI client can touch on a per-key basis.
Customers use the MCP server to bring their business OS into the chat window they already keep open all day.
"Find the deal with Acme Corp, move it to Negotiation, and add a note that they want a 12-month commit." Claude does the three writes. You approve.
Paste a sales-call transcript into Claude, ask for a quotation. Claude calls create_quotation with the right line items, the right contact, the right currency.
"Log 90 minutes against the Acme onboarding project, billable, tagged 'kick-off'." Done. The entry appears in your Workestra timer history.
From Cursor or VS Code: "Show me support tickets touching the auth module from this week, sorted by SLA breach risk." Workestra returns them — Claude triages.
Spin up a workspace, issue a key, paste it into your client's MCP config. From there, every conversation is grounded in your real data.
Free workspace. Workspace-scoped key. Revoke any time.