Blog
Give Claude Code your company's tools in one command
Claude Code can write the code. It cannot read your inbox, your calendar or your CRM. One command connects Cedric and hands it every tool your team has connected.
Benjamin Ben HattarClaude Code is very good at the code. It knows nothing about the rest of the company: the customer who emailed this morning, the meeting at two, the invoice that is late. Every time the work touches those, you leave the terminal, look it up, and paste it back.
Cedric closes that gap in one command. Cedric is an MCP server, and every tool your team has connected to it (Gmail, Calendar, the CRM, Slack, Notion, GitHub, the rest) becomes a tool Claude Code can call. Same rules as in chat: reading is free, anything that sends or changes waits for your yes.
It costs almost nothing. On an MCP call Cedric's own model never runs; Claude Code does the thinking and Cedric runs the tool. A workspace starts with 100,000 free credits and no card.
- 01
Create a Cedric account and connect a tool or two
Go to app.meet-cedric.com, continue with Slack, Discord, Telegram or Google. On Integrations, connect what Claude Code should reach: your inbox, your calendar, the repo host. Each one is a sign-in on the tool's own screen.
- 02
Add Cedric to Claude Code
One line in your terminal: claude mcp add --transport http cedric https://app.meet-cedric.com/api/v1/mcp. No key in the command. The same address is on Admin settings, then MCP, with a Copy button and the line ready to paste.
- 03
Sign in once
In Claude Code, type /mcp, pick cedric, choose Authenticate. A browser tab opens on Cedric's sign-in; sign in, check the workspace name, allow. From then on Claude Code holds the connection and refreshes it on its own.
Working in a script or a CI job with no browser? Admin settings, then MCP, also mints API keys for exactly that.
What it looks like afterwards
"Read the thread from Fenwick about the API limits and open a GitHub issue with the specifics" is one ask. Claude Code searches the inbox through Cedric, reads the thread, drafts the issue, and stops before creating it, because creating it changes something. You say yes in the terminal and it is done.
There is also a shortcut for whole tasks. Cedric exposes one extra tool, ask_cedric, that hands a job to Cedric in full: "chase the three unpaid invoices from August" runs as a Cedric task, with its memory, its connections and its approvals, and Claude Code gets the reply.
Two things to know
The connection acts as you. It can do exactly what you can do in Cedric, in this workspace, and nothing more. Disconnect it any time under Admin settings, then MCP.
Sending, changing and spending still wait for a person. That is Cedric's rule everywhere, and a terminal is no exception.
FAQ
Anything that speaks MCP. The MCP page lists the ones with a one-click setup and shows the exact line or file each one needs.
Each person signs in as themselves. A shared team config carries only the address, so nothing secret ends up in a repo.
Free to start, no card.