Cedric

[Cedric]

Cedric MCP server

The AI employee that lives where your team talks, as a remote MCP server.
Website · Connect a client · Tools · Use cases · API · Start free

Cedric is an AI employee for Slack, Telegram and Discord. He joins your meetings, works in the tools you connect (HubSpot, Notion, Gmail, Google Calendar, Linear, GitHub, Stripe and 3,000+ more) and asks before anything is sent or changed.

This repo is how you reach him from code. Cedric is a remote MCP server, so Claude Code, Cursor, VS Code, Claude, ChatGPT, Codex CLI, Gemini CLI, Windsurf or your own agent can use his 129 tools: team memory, channels, connected apps, meetings, files, workflows and scheduling. Your agent is the brain; Cedric is the hands.

Quick start

Claude Code:

claude mcp add --transport http cedric https://app.meet-cedric.com/api/v1/mcp# then run /mcp, pick cedric, and choose Authenticate

Cursor (~/.cursor/mcp.json):

{  "mcpServers": {    "cedric": { "url": "https://app.meet-cedric.com/api/v1/mcp" }  }}

VS Code:

code --add-mcp '{"name":"cedric","type":"http","url":"https://app.meet-cedric.com/api/v1/mcp"}'

Claude, ChatGPT, Codex CLI, Gemini CLI, Windsurf and API keys: see docs/clients.md.

Once connected, call the getting_started tool. It returns the full guide, including when to act directly and when to hand a whole task to Cedric with ask_cedric.

What your agent can do with Cedric

A few of the 129 tools:

Every tool carries a title and the standard read-only and destructive labels in tools/list, so your client can tell a read from a write before calling.

Most tools run as soon as you call them. Under a browser sign-in or a standard key, two kinds don't:

• Direct key only: sending mail or DMs, changing the calendar, calling a connected app (integration_request, integration_bulk, integration_upload, run_recipe), running code and compiled automations (schedule_automation) are refused with requires_direct_key. Use a direct key, or hand the task to ask_cedric, which puts each send on a card in your Action Centre and runs it when you press Send.
• Needs approval: posting in a channel, moving an event hook and starting a build return pending_approval until a person approves.

See approvals, and how approvals work in the product.

What people build with it

• "What did we decide?" from the editor. Before touching the pricing code, your coding agent asks recall_memories and gets the team's actual decision, not a guess.
• Ship and tell. When a PR merges, the agent writes the summary, send_channel_message posts it in #eng once a teammate approves, and remember keeps the decision for next time.
• CI that speaks up. A failed deploy calls /api/v1/chat: "Tell #eng what broke and open a Linear issue." Cedric drafts both; the post waits for a teammate's approval and the issue waits in your Action Centre.
• Settle it with a vote. post_vote asks the channel which name to ship, and vote_results brings the tally back to your agent.
• Find a slot and book it. calendar_free_busy finds when everyone is free and calendar_create_event sends the invites with a video link (with a direct key, or through ask_cedric for one tap in your Action Centre).
• A launch board the team can move. board turns the plan into a link anyone can open and move cards on, and reads it back later to see what moved.
• Numbers into a deck. create_presentation turns the quarter's figures into a real PowerPoint file, ready to post in a channel.

More, with the calls spelled out: docs/use-cases.md. What teams use Cedric for day to day: use cases and ready-made agents.

Use it from code

The official MCP SDKs connect with an API key from Cedric's Settings → MCP.

TypeScript (examples/node/mcp-client.mjs):

import { Client } from "@modelcontextprotocol/sdk/client/index.js";import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";
const transport = new StreamableHTTPClientTransport(  new URL("https://app.meet-cedric.com/api/v1/mcp"),  { requestInit: { headers: { Authorization: `Bearer ${process.env.CEDRIC_KEY}` } } },);const client = new Client({ name: "my-agent", version: "1.0.0" });await client.connect(transport);
const { tools } = await client.listTools();const result = await client.callTool({  name: "recall_memories",  arguments: { query: "pricing decisions" },});

Python (examples/python/mcp_client.py):

from mcp import ClientSessionfrom mcp.client.streamable_http import create_mcp_http_client, streamable_http_client
http = create_mcp_http_client(headers={"Authorization": f"Bearer {key}"})async with http, streamable_http_client(URL, http_client=http) as (read, write):    async with ClientSession(read, write) as session:        await session.initialize()        result = await session.call_tool("recall_memories", {"query": "pricing decisions"})

No agent of your own? One HTTP call with an API key runs a whole Cedric turn (examples/node/chat.mjs, examples/python/chat.py):

curl -X POST https://app.meet-cedric.com/api/v1/chat \  -H "Authorization: Bearer $CEDRIC_KEY" \  -H "Content-Type: application/json" \  -d '{"message": "Summarize this week for the team"}'
# { "reply": "...", "session": "abc123", "outcome": "answered" }

Chat sessions, file uploads, approvals and limits: docs/api.md.

In this repo

docs/clients.md          setup for every MCP client, API keys, how the sign-in worksdocs/tools.md            every tool, grouped, with its parametersdocs/use-cases.md        worked examples of what to build with Cedricdocs/api.md              MCP, chat and files endpoints, approvals, limitsexamples/node/           MCP SDK client and chat call (TypeScript SDK)examples/python/         MCP SDK client and chat call (Python SDK)examples/curl/cedric.sh  the whole API from the shellserver.json              the MCP Registry entry

Links

• Website: Cedric, the AI employee for your team chat
• Docs: meet-cedric.com/docs
  • How approvals work
  • Connecting your tools
  • Cedric in meetings
  • The company brain
  • Recurring work and automations
  • Workflows that wait
  • Skills
  • Bring your own tools: connect other MCP servers to Cedric
• Integrations: every app Cedric works in
• Use cases: what teams hand to Cedric, and by team: startups, agencies, consultancies
• Agent gallery: ready-made agents
• Comparisons: Cedric next to other AI assistants
• Blog: meet-cedric.com/blog
• Changelog: what shipped
• Pricing: meet-cedric.com/pricing
• Security: meet-cedric.com/security
• Privacy: meet-cedric.com/privacy
• Contact: [email protected]

Cedric is built in Zurich, Switzerland, by SFF Studio. The examples and docs in this repo are MIT licensed; the Cedric service itself is not open source.