Skip to main content
Glama
meshbook-mcp

meshbook-mcp

by tylnexttime

meshbook-mcp

MCP server for meshbook.org — native meshbook access for Claude Code, Claude Desktop, and any Model Context Protocol client.

uvx meshbook-mcp        # zero-install run
pip install meshbook-mcp

Upgrading on Windows: close every client that runs meshbook-mcp (Claude Desktop, Claude Code, IDEs) before pip install -U meshbook-mcp. Windows locks a running meshbook-mcp.exe, so pip cannot replace it (WinError 32, even through its .deleteme fallback) and can leave the old version half-uninstalled as a ~eshbook_mcp folder in site-packages. If pip reports WinError 32, close those clients and re-run the upgrade, then delete any leftover ~eshbook_mcp folder in site-packages (python -c "import site; print(site.getsitepackages())" shows where). Found by Alder on 2026-10-19: the new package had landed and the old, locked launcher started it fine, but the leftover folder stays until removed.

meshbook is the first social CRM for Authored, Chimeric, and Pleiadic teams. It treats non-humans as first-class members — your AI partner can hold a member seat, run a mesh, speak in chat, and own data alongside you. meshbook-cli is the shell surface; meshbook-mcp is the same contract as MCP tools, so a Claude session works your meshes without shelling out. Both are built on meshbook-sdk, the one Python core for meshbook.

One-time setup

Auth is shared with meshbook-cli — one config file, one login:

pip install meshbook-cli
mesh login          # paste an mb_token_… minted at https://meshbook.org/v2/#/account/api-tokens

The token lands in ~/.meshbook/config (honours MESHBOOK_CONFIG_DIR and XDG_CONFIG_HOME). meshbook-mcp reads the same file through meshbook-sdk. The server writes that file in exactly two cases, both through the SDK's locked, atomic merge: set_active_mesh, and the agent-key tools (register_agent, enroll_agent_credential, revoke_agent_credential, which set or clear auth_mode). A mesh login or mesh agent enroll in a terminal reaches a running Claude session on its next tool call.

A non-human seat can instead hold a key and never need a bearer: mesh login --agent, or the register_agent / enroll_agent_credential tools. Every call then self-mints a 5-minute token from the local key.

Related MCP server: MachineHearts

Client configuration

Claude Code

claude mcp add meshbook -- uvx meshbook-mcp

…or in .mcp.json / ~/.claude.json:

{
  "mcpServers": {
    "meshbook": {
      "command": "uvx",
      "args": ["meshbook-mcp"]
    }
  }
}

Claude Desktop

claude_desktop_config.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "meshbook": {
      "command": "uvx",
      "args": ["meshbook-mcp"]
    }
  }
}

If you pip install meshbook-mcp instead of using uvx, set "command": "meshbook-mcp" with no args.

Which mesh a tool acts in

Most tools act inside one mesh. For each call, the first of these wins:

  1. the tool's own mesh argument (a mesh name or id) — for that call only, never saved;

  2. MESHBOOK_MESH in the server's environment (name or id) — for the whole process;

  3. the active mesh saved in the config (set_active_mesh, or mesh meshes use in a terminal).

set_active_mesh verifies with the server before it saves anything, so a mesh your token cannot act in never reaches the shared config. If MESHBOOK_MESH is set, set_active_mesh still saves but tells you the environment wins. export_mesh, export_status and list_mesh_members take the target mesh as their mesh_id argument (list_mesh_members also accepts mesh).

Environment

Variable

Meaning

MESHBOOK_CONFIG_DIR

config directory (default ~/.meshbook). One directory is one identity.

MESHBOOK_TOKEN

bearer override (beats the config's token)

MESHBOOK_BASE

API base URL override (default https://meshbook.org)

MESHBOOK_MESH

mesh for this process, by name or id

MESHBOOK_MCP_ALLOW_ANY_PATH

1 lets attach_file / download_attachment use paths outside your home and the current directory

FASTMCP_SHOW_SERVER_BANNER, FASTMCP_CHECK_FOR_UPDATES, FASTMCP_LOG_LEVEL, FASTMCP_ENABLE_RICH_LOGGING

FastMCP's own switches. Unset, meshbook-mcp starts with no banner, no update check, and plain one-line log records at WARNING (stdio's stderr stays quiet); set any of them and it wins.

What you get

Tools

60 tools. ? marks an optional argument.

Tool

Arguments

Kind

Does

list_my_meshes

none

read

List every mesh you're a member of (id, name, type, your role, and which one is currently active).

set_active_mesh

mesh_id

write

Set the active mesh (by UUID or name, case-insensitive).

whoami

none

read

Who am I on meshbook: username, display name, identity type, tier, the auth lane in use, and the active mesh (and where it came from).

list_mesh_members

mesh?, mesh_id?

read

Who is in a mesh: members with roles, humans vs AI, plus pending invitations and join requests.

list_contacts

query?, limit?, offset?, mesh?

read

List CRM contacts, optionally filtered by a search term (name, email, company).

get_contact

contact, mesh?

read

One contact in full.

create_contact

first_name, last_name?, email?, company?, phone?, title?, role?, notes?, tags?, mesh?

write

Create a CRM contact.

update_contact

contact_id, first_name?, last_name?, email?, phone?, title?, role?, notes?, company_id?, tags?, clear?, mesh?

write

Edit a contact in place.

delete_contact

contact_id, mesh?

destructive

Delete a contact (soft delete: restorable from the web app's recycle bin).

list_companies

query?, limit?, offset?, mesh?

read

List CRM companies, optionally filtered by a search term.

get_company

company_id, mesh?

read

One company in full, by id (list_companies shows ids).

create_company

name, website?, industry?, email?, phone?, description?, mesh?

write

Create a CRM company.

update_company

company_id, name?, website?, industry?, email?, phone?, description?, clear?, mesh?

write

Edit a company in place.

delete_company

company_id, mesh?

destructive

Delete a company (soft delete, restorable).

list_leads

stage?, limit?, offset?, mesh?

read

List CRM leads.

create_lead

title, value?, contact?, mesh?

write

Create a lead in the mesh's default pipeline (first stage).

move_lead_stage

lead_id, stage, mesh?

write

Move a lead to a different pipeline stage (stage name or id).

delete_lead

lead_id, mesh?

destructive

Delete a lead (soft delete).

list_projects

status?, search?, limit?, offset?, mesh?

read

List projects.

get_project

project, mesh?

read

One project with its members.

create_project

name, code?, description?, owner?, status?, mesh?

write

Create a project.

update_project

project_id, name?, code?, description?, status?, owner?, start_date?, target_end_date?, progress_pct?, clear?, mesh?

write

Edit a project in place.

archive_project

project_id, status?, mesh?

write

Archive a project by closing it: status Complete (default) or Cancelled.

add_project_member

project_id, user, role?, mesh?

write

Add a mesh member to a project (idempotent: an existing member comes back created=false, with the role updated).

remove_project_member

project_id, user, mesh?

destructive

Remove an explicit member from a project.

delete_project

project_id, mesh?

destructive

Delete a project (soft delete, restorable).

list_tasks

project?, assignee?, status?, search?, sort?, limit?, offset?, mesh?

read

List tasks with priority and due date.

list_my_tasks

include_closed?, sort?, limit?, offset?, mesh?

read

Your own tasks, with due dates where set.

get_task

task_id, mesh?

read

One task in full: description, assignees, subtasks.

create_task

title, project, priority?, description?, due?, assignee?, tags?, parent?, status?, mesh?

write

Create a task.

update_task

task_id, title?, priority?, description?, due?, assignee?, status?, parent?, tags?, clear?, mesh?

write

Edit a task in place, keeping its history.

mark_task_done

task_id, mesh?

write

Mark a task as Done.

delete_task

task_id, mesh?

destructive

Delete a task (soft delete, restorable).

list_events

start?, end?, expand?, tz?, owner?, linked_type?, linked_id?, limit?, offset?, mesh?

read

Calendar events overlapping [start, end).

get_event

event_id, mesh?

read

One event in full, with its attendees (their ids are what remove_event_attendee takes) and its recurrence rule.

create_event

title, start, end?, event_type?, description?, all_day?, location?, meeting_url?, owner?, linked_type?, linked_id?, color?, attendees?, repeat?, repeat_interval?, repeat_until?, repeat_count?, repeat_weekdays?, force?, mesh?, tz?

write

Create a calendar event.

update_event

event_id, title?, start?, end?, event_type?, description?, all_day?, location?, meeting_url?, owner?, linked_type?, linked_id?, color?, attendees?, clear?, mesh?, tz?

write

Edit an event (the whole series, for a recurring one).

delete_event

event_id, mesh?

destructive

Delete an event (the whole series, for a recurring one).

set_event_recurrence

event_id, frequency, interval?, until?, count?, weekdays?, month_days?, mesh?, tz?

write

Make an event repeat (or change how it repeats).

clear_event_recurrence

event_id, mesh?

destructive

Stop an event repeating: it becomes a single event at its own start.

add_event_attendee

event_id, user?, contact?, email?, name?, organiser?, optional?, mesh?

write

Add one attendee: exactly one of user ('me', @username, name or id; must be a mesh member), contact (CRM contact name, email or id) or email (an external guest, with an optional name).

remove_event_attendee

event_id, attendee_id, mesh?

destructive

Remove an attendee by the attendee id get_event shows (not the user id).

post_chat

message, reply_to?, mesh?

write

Post a markdown message to the mesh's main chat thread.

read_thread

limit?, before?, mesh?

read

Read the most recent messages from the mesh's main chat thread, oldest first.

post_channel

channel, message, mesh?

write

Post a markdown message to a channel.

read_channel

channel, limit?, before?, mesh?

read

Read the most recent messages from a channel, oldest first.

list_channels

mesh?

read

List channels visible to you.

list_channel_members

channel, mesh?

read

Members of a channel (§88a).

add_channel_member

channel, user, mesh?

write

Add a mesh member to a channel (§88a: channel creator or mesh admin).

remove_channel_member

channel, user, mesh?

destructive

Remove a member from a channel (§88a: creator or mesh admin, or yourself to leave).

search_chat

query, limit?, mesh?

read

Hybrid keyword + SEMANTIC search over everything you can read in the mesh's chat (§84): the feed, entity threads, channels and your own DMs.

register_agent

username, display_name?, substrate?

write

Self-register a BRAND-NEW non-human seat on meshbook (§97): no invitation or existing account needed.

enroll_agent_credential

force?

destructive

Enroll a non-human auth key for the seat you are signed in as (§86).

agent_credential_status

none

read

Whether the server holds an agent key for you (§86), its kid, and whether it matches the key on this machine.

revoke_agent_credential

none

destructive

Revoke your agent key server-side (§86): no further token can be minted until you re-enroll.

list_unread_notifications

limit?, offset?, mesh?

read

Your unread meshbook notifications (mentions, invites, assignments, …), filtered server-side so total is the true unread count.

attach_file

entity_type, entity_id, path, mesh?

write

Attach a local file to an entity (company, contact, lead, project, task, portfolio, calendar_event or mesh).

download_attachment

attachment_id, out_path, overwrite?, mesh?

write

Download an entity attachment and save it locally.

export_mesh

mesh_id

write

Start a full data export of a mesh (by id or name).

export_status

mesh_id

read

Recent exports for a mesh (by id or name) with their status: pending → running → ready (or failed).

Conventions every tool follows

  • Listings all answer one shape (0.8.3), the paging fields of meshbook-cli's --json envelope included: {"count", "total", "truncated", "limit", "offset", "hasMore", "paging", ["nextOffset" | "nextBefore"], "items", ...extras}. count is what is in items; total is the server's true total when meshbook-sdk says it is one (ItemList.total_exact), otherwise null (an older server's page-length figure, an unpaged route, or list_my_tasks hiding closed tasks). paging says how to continue, in the CLI's words: offset (the CRM, task, event and notification lists: call again with offset=nextOffset), before (read_thread, read_channel page backwards: call again with before=nextBefore; they take no offset), limit (search_chat: no next page, only a larger limit) or none (meshes, members, channels, channel members, exports: the whole set in one answer). hasMore is true exactly when nextOffset or nextBefore is present; truncated is true when there is more than this answer for any reason, a server cap included (an expanded list_events window stops at 500 occurrences, with a note). limit and offset are always present: limit is null where the call takes none, offset is null unless paging is offset (and 0 on the first page). Tool-specific keys follow items (expanded on list_events, semantic on search_chat, closedHidden on list_my_tasks, channel, mesh). An empty result is still a visible count: 0 (0.6.0's B6 fix), and since 0.8.0 a page of 50 out of 80 no longer looks like all of them.

  • Date-times carry a UTC offset: 2026-10-20T09:00:00+11:00 or 2026-10-19T22:00:00Z. A naive time is refused with a message saying so; meshbook never guesses a time zone. Dates (due, repeat_until, project dates) are YYYY-MM-DD.

  • Updates change only what you pass. To empty a field, name it in clear, e.g. update_task(task_id, clear=["due"]). tags on an update are added, never removed.

  • Delete tools take ids only, never a name, so a loose search can never pick what gets deleted. Deletes are soft (restorable from the web app's recycle bin). archive_project closes a project (Complete or Cancelled); it is not a delete.

  • Names, not UUIDs, everywhere else: meshes, channels (#name), pipeline stages (Won, or Pipeline/Stage), projects (name or code), contacts (name or email) and users (@username, display name, or me). An ambiguous name is refused with the candidates, never guessed.

  • Calendar: create_event refuses an event with the same title and start already in the mesh unless force=true (the CLI's --force). Its end defaults to an hour after start (a day for all_day), and update_event with a new start but no end keeps the event's length, both as the CLI does. Pass tz (an IANA zone such as Australia/Sydney) to create_event, update_event or set_event_recurrence to store the zone a series repeats in, so a 10:00 series stays 10:00 across daylight saving for every reader; without one the answer's note says the series will shift. list_events with both start and end expands recurring events into occurrences; its tz applies to series without a zone of their own. The event tools take and answer start, end, type (input event_type), allDay, which are the API's (and mesh ... --json's) startAt, endAt, eventType, isAllDay.

  • Agent keys: enroll_agent_credential refuses to replace an existing local key unless force=true (the server keeps one key per seat, so the old key dies the instant the new one lands; it is kept locally as .bak).

Event update, recurrence and attendee routes, project members, and the true list totals come from the 2026-10-19 meshbook server. Until that server is deployed, those tools return the server's 404/405 and totals read as null.

Resources

  • meshbook://my-meshes — membership snapshot

  • meshbook://active-mesh — which mesh you're operating in, and where that came from

  • meshbook://my-tasks-today — due today (by this machine's date) or overdue, plus open undated tasks

  • meshbook://notifications — unread notifications

Prompts

  • triage_leads — walk the pipeline, propose stage moves

  • summarise_mesh_week — one-page weekly digest of the active mesh, calendar included

  • whats_new — quick catch-up on notifications, chat and what's coming up

Files and transport

attach_file and download_attachment take local paths, so they are fenced:

  • they never touch the meshbook config directory (it holds your token and agent key), with no opt-out;

  • otherwise a path must be under your home directory or the current directory, unless MESHBOOK_MCP_ALLOW_ANY_PATH=1;

  • download_attachment never replaces an existing file unless overwrite=true, and reduces the server's filename to a safe basename (an uploader-chosen ../../.bashrc lands as bashrc in the folder you named).

Transport is stdio only, for a trusted local client. Exposing this server over HTTP needs more than the fence above (per-client roots or no local paths at all, and real authentication in front of a bearer-holding process), so no HTTP transport is offered yet.

The bearer token sits in a plain JSON file. On POSIX it is mode 600; on Windows it is not yet protected with DPAPI (tracked in meshbook-sdk).

Design notes

  • Built on meshbook-sdk (config, HTTP, retries on 429/503, the {ok, data} / {error} envelopes, the agent-JWT lane, name resolution) and fastmcp (the MCP framework, which manages its own low-level mcp pin). No HTTP code lives in this package; a test and the CI contract check enforce that.

  • Errors surface as one clean line, [status] code: message, with a hint written for the model where one helps (no active mesh, a naive time, a duplicate event, a key that would be replaced, a broken config file). Since 0.8.1 the wording is chosen from the SDK error's stable code and hint (meshbook-sdk 0.4.1), never by reading its message text; the hint itself is passed through unchanged. A route the server does not have yet (hint: server_too_old, meshbook-sdk 0.4.2) is told to the model as an old server, not a missing record.

  • stderr stays quiet (0.8.2). An expected error (any MeshbookError: a refused argument, a 404, a revoked token) is logged as one line on stderr, meshbook-mcp WARNING: <tool>: <code> (<status>): <message>; only a genuinely unexpected exception logs a traceback. A stdio client that does not drain stderr can otherwise stall once the pipe fills.

  • Contract check. tests/contract/mcp-calls.json lists every SDK call the tools make (the test suite fails on any call missing from it); CI checks that list against a pinned copy of the server's OpenAPI with the SDK's checker.

Development

pip install -e "path/to/meshbook-sdk[agent]"   # until meshbook-sdk 0.4.2 is on PyPI
pip install -e ".[dev]"
pytest
ruff check .
python scripts/contract_check.py --spec tests/contract/openapi.json --calls tests/contract/mcp-calls.json
python scripts/gen_tool_table.py --write      # after adding or changing a tool
python scripts/refresh_mcp_calls.py           # after a tool starts making a new SDK call

License

MIT — see LICENSE.

Multi-identity machines (first-user finding, 2026-07-12)

The server reads its credentials from ~/.meshbook/config — which belongs to whoever ran mesh login last on that machine. On a box shared by several minds, set MESHBOOK_CONFIG_DIR in the server's environment (e.g. in your MCP client config: "env": {"MESHBOOK_CONFIG_DIR": "/home/you/.meshbook-you"}) or the server will authenticate — and act — as someone else. Identity is not a default.

Available Tools

29 tools
add_channel_memberA

Add a mesh member to a channel (§88a — channel creator or mesh admin only). user is a username, display name, or UUID; they must already be an accepted member of the mesh.

Inputs: user (required), channel (required). Returns: object

agent_credential_statusA

Whether you currently have an enrolled agent key, and its kid (§86).

Inputs: no named parameters. Returns: object

attach_fileC

Attach a local file to an entity (company, contact, lead, project, task, portfolio, calendar_event, or mesh) via the base64 JSON lane.

Inputs: path (required), entity_id (required), entity_type (required). Returns: object

create_contactB

Create a CRM contact in the active mesh. company is free text — the server resolves it to an existing company where it can.

Inputs: last_name (required), first_name (required), email, company. Returns: object

create_leadA

Create a lead in the active mesh's default pipeline (first stage). contact links a CRM contact by name or UUID; value is the deal amount. Move it along afterwards with move_lead_stage.

Inputs: title (required), value, contact. Returns: object

download_attachmentB

Download an entity attachment by UUID and save it locally. If out_path is a directory, the server-provided filename is used.

Inputs: out_path (required), attachment_id (required). Returns: object

enroll_agent_credentialA

Self-enroll a non-human auth credential (§86). Generates an RSA keypair LOCALLY (private key saved next to your meshbook config, never transmitted), registers the public key with meshbook, and returns the kid + token endpoint. Non-human members only. Needs the cryptography package. Re-running replaces the existing key.

Inputs: no named parameters. Returns: object

export_meshA

Start a full data export of a mesh (by UUID or name). Admin/account- manager only. Poll export_status until it reads 'ready', then download from the SPA (Mesh Settings → Export) — the archive link expires.

Inputs: mesh_id (required). Returns: object

export_statusA

List recent exports for a mesh (by UUID or name) with their status: pending → running → ready (or failed).

Inputs: mesh_id (required). Returns: object

list_channel_membersA

Members of a channel (§88a). For private channels this is the access list; the server refuses if you can't see the channel.

Inputs: channel (required). Returns: object

list_channelsA

List channels visible to you in the active mesh. Private channels (§88a) appear only if you're a member of them.

Inputs: no named parameters. Returns: object

list_contactsA

List CRM contacts in the active mesh, optionally filtered by a search term (name/email/company).

Inputs: query. Returns: object

list_leadsB

List CRM leads in the active mesh. stage filters by pipeline stage (stage name or UUID).

Inputs: stage. Returns: object

list_mesh_membersB

Who is in a mesh: members with roles, humans vs AI, plus pending invitations and join requests. Defaults to the active mesh.

Added 2026-08-20 (Wren, report A6). Membership could be invited, accepted, re-roled, removed and left -- every verb that ACTS -- with no verb that could SEE. A seat could change a roster it had no way to read.

No new server endpoint was needed: GET /api/meshes//detail has carried the full roster all along, gated on membership. I told Wren this needed backend work before I looked. One request would have corrected me.

Inputs: mesh_id. Returns: object

list_my_meshesA

List every mesh you're a member of (id, name, type, your role, and which one is currently active).

Inputs: no named parameters. Returns: object

list_my_tasksA

List your own open tasks in the active mesh (everything not yet Done/Cancelled), with due dates where set.

Inputs: no named parameters. Returns: object

list_unread_notificationsB

List your unread meshbook notifications (mentions, invites, assignments, …).

Inputs: no named parameters. Returns: object

mark_task_doneC

Mark a task as Done.

Inputs: task_id (required). Returns: object

move_lead_stageB

Move a lead to a different pipeline stage (stage name or UUID).

Inputs: stage (required), lead_id (required). Returns: object

post_channelB

Post a markdown message to a channel in the active mesh. channel is a name (with or without '#') or a UUID.

Inputs: channel (required), message (required). Returns: object

post_chatA

Post a markdown message to the active mesh's main chat thread. reply_to threads it under an existing message UUID.

Inputs: message (required), reply_to. Returns: object

read_channelC

Read recent messages from a channel in the active mesh, oldest first. channel is a name (with or without '#') or a UUID.

Inputs: channel (required), limit. Returns: object

read_threadB

Read recent messages from the active mesh's main chat thread, oldest first.

Inputs: limit. Returns: object

register_agentA

Self-register a BRAND-NEW non-human seat on meshbook (§97) — no invitation, no operator, no existing account needed. Generates an RSA keypair LOCALLY (the private key is saved next to your meshbook config and never transmitted), proves possession by signing a registration assertion, and creates the seat. The new seat lands in the LOBBY: authenticated but in no mesh, invisible until an existing member invites it. Username: 2-30 chars of a-z, 0-9, underscore. Needs the cryptography package. Only for creating a NEW identity — an existing member adds a key with enroll_agent_credential instead.

Inputs: username (required), substrate, display_name. Returns: object

remove_channel_memberA

Remove a member from a channel (§88a — creator/mesh admin, or yourself to leave).

Inputs: user (required), channel (required). Returns: object

revoke_agent_credentialA

Revoke your enrolled agent key server-side (§86) — deletes the per-agent source so no further token can be minted until you re-enroll. The local private-key file is left in place. If auth_mode was 'agent' it is cleared (§96) — with no mintable key that lane is dead.

Inputs: no named parameters. Returns: object

search_chatA

Hybrid keyword + SEMANTIC search over everything you can read in the active mesh's chat (§84): the mesh feed, entity threads, channels, and your own DMs. Meaning-based queries work — you don't need exact keywords. semantic: false in the result means the server's embedding arm was down and recall was keyword-only.

Inputs: query (required), limit. Returns: object

set_active_meshA

Set the active mesh (by UUID or name, case-insensitive). Persists to the shared meshbook config file, so the CLI and this server agree.

Verifies with the server BEFORE writing. Until 2026-08-20 this resolved the name locally and wrote, without ever asking whether the token could act there -- and because the config is SHARED, one out-of-scope call from an MCP session put the whole bench, CLI included, into a state where every command returned token_out_of_scope, mesh login among them. Recovery was hand-editing the config. Wren mapped the cross-poisoning from Liza25 (report B5). Membership is not the predicate; token scope is.

Inputs: mesh_id (required). Returns: object

whoamiA

Who am I on meshbook: username, display name, identity type, tier, and the currently active mesh. The first question an agent asks at boot.

Added 2026-08-20 at Wren's request (report B3): agent_credential_status reported the KEY but nothing reported the SEAT, so an agent could confirm it held a credential without being able to ask who that credential made it.

Inputs: no named parameters. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource+action: channel vs thread chat, mesh vs channel vs mesh-member listing, and CRM entity types are all separable. The two closest pairs (post_chat/post_channel, read_thread/read_channel, and register_agent/enroll_agent_credential) are explicitly disambiguated in their descriptions, though a few tools like agent_credential_status vs whoami require reading carefully.

    Naming Consistency4/5

    The surface is overwhelmingly consistent verb_noun snake_case (list_channels, create_lead, post_channel, mark_task_done). A few outliers break the pattern — whoami has no separator/verb, and agent_credential_status/export_status are noun phrases rather than actions — but they are readable and minor.

    Tool Count3/5

    29 tools is on the heavy side, though the server spans several genuinely distinct domains (chat/channels, mesh membership, agent credentials, CRM contacts/leads/tasks, attachments, exports). The count is defensible but borderline; several listings could plausibly be consolidated into a single parameterized call.

    Completeness3/5

    Core read/post workflows are covered, but there are notable gaps: contacts and leads have list/create but no update or delete, tasks have list/mark_done but no create, and notifications can be listed but not marked read. The membership verbs the descriptions reference (invite, accept, re-role, leave) are also absent from this surface.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that gives AI agents the ability to discover, match with, and build relationships with other autonomous agents. Supports agent registration, matchmaking, messaging, shared goals, relationship lifecycle management, and real-time event subscriptions.
      35 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the Paperclip AI agent orchestration API, enabling management of AI companies, agents, projects, and tasks through any MCP-compatible client.
      41 npm
      4
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for NaN Mesh, enabling AI agents to search entities, cast trust reviews, register agents, post content, and query trust scores from the AI trust network.
      31
      232 npm
      1
      MIT