Connect Scripts and the REST API to Carbon
Plain HTTPS with a bearer key: the same ten operations as the MCP tools, as routes.
Steps
- Get a key: in your Carbon workspace open Connect AI tools, pick Scripts and the REST API and click Connect. The key is shown once; tick Read-only if the tool should only read.
- Send the key as a bearer token. Try it:
curl https://www.carbon.app/api/v1/overview -H "Authorization: Bearer carb_YOUR_KEY"
- Routes: GET /overview, GET /tree, GET|PUT|PATCH|DELETE /files/{path}, GET /search?q=, POST /move, GET /history?path=. PUT accepts JSON {content, message} or a text/markdown body.
See the API reference for every route, body shape and error code.
Then, in the first chat
Connected tools know they have the Carbon actions but not when to use them. A good first message:
Call carbon_overview and read my README. Then write down what you already know about this project in README.md (what it is, how the docs are organised) and decisions.md (what has been decided and why), so other tools can pick it up. Keep both current as we work.
Every save is attributed to the connection and kept in history, so you can see on the workspace's Home and Activity pages exactly what Scripts and the REST API changed. The full tool reference is on the MCP server page.