Coherence

Created By
getcoherence23 days ago
MCP (Model Context Protocol) server that exposes Coherence as tools for Claude, Cursor, Cline, and other MCP-compatible clients.
Overview

@coherenceos/mcp-server

MCP (Model Context Protocol) server that exposes Coherence as tools for Claude, Cursor, Cline, and other MCP-compatible clients.

The headline: chat_with_agent — send a message to your Coherence agent (Nash) from Claude Desktop and it can draft emails, create reminders, update records, post to social, create landing pages, and more, all under your workspace's approval rules.

Quickstart

1. Create an API key

In Coherence, go to Settings → API Keys → Create new key. Copy the sk_live_… value — it's only shown once. The Coherence UI will hand you a ready-to-paste JSON snippet that you can drop straight into your MCP client config.

2. Add to your MCP client

Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):

{
  "mcpServers": {
    "coherence": {
      "command": "npx",
      "args": ["-y", "@coherenceos/mcp-server"],
      "env": {
        "COHERENCE_API_URL": "https://api.getcoherence.io/v1",
        "COHERENCE_API_TOKEN": "sk_live_..."
      }
    }
  }
}

Cursor / Cline / Continue / Windsurf: same JSON, dropped into each tool's MCP settings file.

3. Talk to your workspace

Restart your MCP client, then try:

"Ask my Coherence agent to draft a follow-up email to the leads I created this week."

"List my open deals over $50k."

"Create a contact for Jane Doe at Acme Corp, then remind me to follow up next Tuesday."

Available tools

ToolWhat it does
chat_with_agentSend a message to a Coherence agent; the agent uses its own toolset (email, reminders, calendar, social, landing pages, approvals, etc.) and returns its response
list_modulesList CRM modules in the workspace
list_module_fieldsList fields on a module — useful before creating/updating records
list_recordsList records in a module with search + pagination
get_recordGet a single record by ID
create_recordCreate a new record
update_recordUpdate a record's fields
delete_recordSoft-delete a record (recoverable from trash)
list_outreach_itemsList blog articles, LinkedIn posts, emails, etc.
get_outreach_itemGet a single outreach item, including its MDX content
create_outreach_itemCreate a new outreach item
update_outreach_bodyUpdate the MDX body of an outreach item
update_outreach_itemUpdate outreach metadata (title, status, etc.)

For everything else — calendar events, sending email, posting to social, creating landing pages, managing approvals — use chat_with_agent. The agent has the full toolset.

Environment variables

VariableRequiredDefaultDescription
COHERENCE_API_TOKENYesAPI key (sk_live_…) from your Coherence workspace
COHERENCE_API_URLNohttps://api.getcoherence.io/v1API base URL

Scopes

When you create an API key in Coherence you can pick scopes. If you tick none, the key inherits your full user permissions (the default). If you tick some, the key is restricted to those:

  • records:read, records:write — module records
  • collab:read, collab:write — Collab documents
  • agents:read, agents:write — agents and chat_with_agent
  • workspace:read — modules, fields, workspace metadata

Approval gates (sendEmail, postToSocial, etc.) are enforced inside the Coherence platform regardless of which scopes a key holds — an API key cannot bypass them.

Server Config

{
  "mcpServers": {
    "coherence": {
      "command": "npx",
      "args": [
        "-y",
        "@coherenceos/mcp-server"
      ],
      "env": {
        "COHERENCE_API_URL": "https://api.getcoherence.io/v1",
        "COHERENCE_API_TOKEN": "<YOUR_API_KEY>"
      }
    }
  }
}
Project Info
Created At
23 days ago
Updated At
7 days ago
Author Name
getcoherence
Star
-
Language
-
License
-
Category
Tags

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago