Docs · Integrations
If your tool speaks MCP, Cedric can use it.
MCP is an open standard that lets tools describe what they can do. Point Cedric at yours and its abilities join the toolbox, under the same rules as everything else.
- MCP is an open standard, not a Cedric invention: many tools, internal platforms, and agents already speak it.
- Connecting takes a message: give Cedric the server's address and key, and its tools appear.
- Connected tools follow the house rules: reading is free, anything with consequences asks first.
- Access is scoped to your workspace and revocable in one place.
- If a connected server goes down, Cedric carries on without it. A broken tool never breaks the task.
The integration you don't have to wait for
No product ships every integration, and your most important tool might be the internal one nobody else has. MCP closes that gap: any tool that speaks the standard can join Cedric's toolbox without anyone waiting for us.
Once connected, there is no second-class citizenship. The new tools sit next to the built-in ones, show up in the same tasks, and answer to the same approval gate.
Connect it
The toolbox
Same rules as everything
Tomás Rivera
Roll us back to yesterday's release.
CedricApp
Rollback prepared through your deploy server. This changes production.
The loop: an internal deploy server registered in one message, its tools joining the toolbox, and a rollback still waiting for a human yes.
Connect it
The internal tool, connected in a message.
Kevin Zhou9:14 AM
@Cedric connect our deploy server, it speaks MCP: tools.internal/mcp
CedricAPP9:15 AM
Connected. It offers three tools: deploy status, release notes, and rollback. Reading is free; a rollback changes production, so it will always ask first.
A minute, not a project
Address and key, done. The server tells Cedric what it can do; nobody writes glue code.
The gate travels
Cedric classifies what each new tool can touch. Risky abilities inherit the approval gate automatically.
Revocable in one place
The connection is workspace-scoped. Remove it and every one of its tools disappears with it.
Use it
New tool, same rules.
Tomás Rivera10:02 AM
@Cedric roll us back to yesterday's release.
CedricAPP10:03 AM
Rollback prepared through your deploy server: yesterday's release, current one kept for a fast return. This changes production, so it waits for a yes.
No special cases
A tool you connected this morning behaves exactly like one that shipped with Cedric, approvals included.
Failure stays contained
If the server is unreachable, Cedric says so and finishes what it can. One tool being down never sinks the task.
The team sees it work
The connection, the proposal, and the yes all happen in the channel, so the audit trail writes itself.
Connecting a server
Three inputs, and the third is optional.
- 01
Find the address
Your tool's MCP endpoint, usually one line in its docs or from whoever built the internal service.
- 02
Tell Cedric to connect it
In chat or from the dashboard, with the access key if the server wants one. The key stays scoped to your workspace.
- 03
Watch the tools appear
Cedric lists what the server offers and starts using it where it helps. Ask "what can you do with our deploy server?" any time.
FAQ
No, it is an open standard adopted across the industry. Tools that speak it work with Cedric and with other assistants; nothing locks you in.
No. The approval gate sits under every tool, connected or built-in. Anything that sends, changes, or spends waits for a person.
The connection belongs to the workspace, like other team connections, and can be removed by the team in one place.
Its tools simply sit out that task. Cedric notes what was unavailable instead of failing the whole job.
Ready when you are
Plug in the tool we haven't met.
Add Cedric, connect what you already use, and point it at your own servers too. $50 in free credits, no card needed.
$50 in free credits, no card needed.