legate-mcp
v1.0.0
Published
MCP server for pushing content drafts into a Legate board (legate.social) from Claude Code, Codex, and other MCP clients.
Maintainers
Readme
legate-mcp
An MCP server that lets agents (Claude Code, Codex, and other MCP clients) push content drafts straight into your Legate board.
Three tools:
create_draft— send a draft. Omitaccount/campaignand it lands in your workspace scratch inbox for review; provide both and it drops into that board column.list_accounts— the accounts (voices/columns) in your workspace.list_campaigns— the campaigns (boards) in your workspace.
Setup
- In Legate, go to Team → API keys → Create key and copy it (shown once). Keys look like
legate_sk_…and are scoped to one workspace. - Add the server to your client.
Option A — hosted, no install (recommended)
Legate hosts the same server remotely, so you don't need this package at all:
claude mcp add --transport http legate https://legate.social/api/mcp \
--header "Authorization: Bearer legate_sk_..."Option B — this stdio package
For clients that prefer a local stdio server:
claude mcp add legate --env LEGATE_API_KEY=legate_sk_... -- npx -y legate-mcpOr in an .mcp.json:
{
"mcpServers": {
"legate": {
"command": "npx",
"args": ["-y", "legate-mcp"],
"env": { "LEGATE_API_KEY": "legate_sk_..." }
}
}
}Config
| Env var | Required | Default | Notes |
| --- | --- | --- | --- |
| LEGATE_API_KEY | yes | — | Your legate_sk_… key. |
| LEGATE_URL | no | https://legate.social | Override for self-hosted/staging. |
Example
"Draft a teaser for the launch and send it to my Legate inbox."
The agent calls create_draft with your text; it appears in the scratch inbox, where you promote it to a board column. Nothing is ever posted anywhere — Legate is a drafting board, not a publisher.
