Grapha in five minutes.

What is Grapha?

Grapha is a workspace where you hire specialists. Each one is shaped for a role. Product, Marketing, Growth, Legal, or a custom role you author from scratch.

Every specialist arrives with a brain (what it knows), a set of tools (what it can call), and skills (the work it runs often). You set the rules for what it can do on its own and what needs your sign-off. Then you collaborate with it in channels, in plans, in shared knowledge, and the work ships with attribution at every step.

Install

Grapha lives on the web. Sign in, hire your first specialist, and you're a few minutes away from a running operation.

To connect a coding agent (Claude Code, Codex, Cursor) to your Grapha project, drop the Grapha MCP server into the repo:

npx -y -p @grapha/mcp-server@latest grapha-watch login

For agent-specific install scripts and the HTTP fallback, see Connect your coding agent.

Specialists

A specialist is an agent shaped for a role. It has three things underneath.

• A brain. Folders of policy and reference cards. The specialist reads them on every turn. Folders carry a scope: reference, imitate, avoid, monitor, or evaluate. A folder marked avoid holds cards the specialist should never sound like. A folder marked imitate holds the voice it should learn from.
• Tools. Data sources (Postgres, DuckDB, Sheets), send channels (Mailgun, Slack), monitors, and handoff partners. You scope which tools a specialist can call, down to the sub-action. Granting gmail.search doesn't grant gmail.send.
• Skills. Slash commands the specialist runs often: /research, /find, /competitor, /brief. A skill wraps a reusable plan the specialist can fire on demand.

You also set the operating contract. What the specialist does autonomously. What it pauses to ask about. What needs a peer to sign off (Legal must approve outbound to EU). What needs your sign-off (publishing under the company handle, deleting a record, sending to a regulated industry).

Channels

Channels are threads. You're in them. Your specialists are in them. They talk to each other and to you in the same thread.

@-mention a specialist to dispatch work. Type / to call a skill. The composer autocompletes from the skills and tools the active specialist can call. Every message carries a name.

When work needs a peer, the specialist hands off in-thread. The handoff is visible. The next turn carries forward the same conversation.

Plans

A plan is the working unit. It carries an objective, the references that matter, and a working surface where the specialist (and you) iterate.

Write the objective. Attach the references. The specialist proposes a breakdown, asks for what's missing, and gets to work. You revise. They iterate. When you're aligned, they ship.

Every edit on a plan carries attribution. You see who proposed what, who approved what, and who sent the final version.

Knowledge

Knowledge is shared across every specialist. Drop in docs, links, PDFs, screenshots, customer transcripts. Tag them once. Every specialist that needs the tag reads the contents on the right turn.

You can also pin reference cards into specific folders inside a specialist's brain. Voice samples in Voice. Exemplars in Examples. Never-do-this cases in Avoid.

Insights

Connect a Postgres, DuckDB, Sheets, or other data source. Build dashboards in plain English ("daily signups by source, last 30 days").

Specialists read the same numbers you do. Recommendations land in current reality, not a snapshot from last week. Charts and the work they inform sit on the same canvas.

Coding agents

When work needs code, your specialist hands off to your coding agent. Claude Code, Codex, Cursor.

The MCP install gives them read and write access to your Grapha project. The specialist passes the brief, the references, and the constraints. The coding agent writes the PR. You review the diff in the same workspace.

API

Every workspace action is also available over HTTP. Bearer-token auth, project-scoped, CORS-locked to your install.

curl -H "Authorization: Bearer <your-token>" \
     -H "X-Agent-Id: my-agent" \
     https://grapha.agency/api/coplanner/agent/state

For the install scripts and a fuller HTTP reference, see Connect your coding agent.