This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 3, 2026 · mcp.pym.so
45tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.pym.so/mcp
Skill page: https://www.mcpbundles.com/skills/pym-mcp-c02497d85b
Explore capabilities (45)
other 25
Showing 25 of 45
Showing 25 of 45 tools from the public preview. Connect the server to inspect the full live tool list.
Pym Whoami — The authenticated Pym identity (id, org, handle).
Pym List Channels — List channels the caller is an active member of (id, name, scope).
Pym List Messages — Recent messages in a channel (oldest→newest). Use sinceSeq to page forward.
Pym Post Message — Post a message into a channel (e.g. report dev-loop progress / a finished task). Goes through the action queue.
Pym Get Vault — The channel's Live Vault markdown (the maintained state-of-the-channel memory).
Pym Regenerate Vault — Regenerate the channel's Live Vault from its conversation (needs server AI configured).
Pym Update Vault — Write the channel's STATUS doc (markdown) directly — a connected agent maintains the channel's living memory (decisions, open questions, state). Keep it current after meaningful changes.
Pym List Tasks — List tasks. Omit channelId for the cross-scope inbox (every active scope) — the dev-loop poll. Filter by status (backlog|triage|todo|in_progress|review|done|cancelled) or assignee (identityId).
Pym Get Task — A task with its PROVENANCE: cross-domain links + the action(s) that created/touched it.
Pym Create Task — Create a task (one atomic action bundle). With a connected-agent (scoped) token the bundle lands PROPOSED — a 202 with actionId — until a human approves it in Pym. Optional links forge cross-domain edges in the SAME transaction (e.g. {toType:'contact',toId,rel:'about'}).
Pym Update Task Status — Move a task's status (the dev-loop: todo → in_progress → done). Load-merges so other fields survive.
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
404: NOT_FOUND is an MCP server at mcp.pym.so. MCPBundles discovered 45 tools on the live endpoint.
How do I connect 404: NOT_FOUND to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
How many tools does 404: NOT_FOUND provide?
Operate this server?
Request removal if you do not want 404: NOT_FOUND listed here, or claim the listing if you want to manage it on MCPBundles.
Operate 404: NOT_FOUND?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
More in developer tools
Other MCP servers in this category from the directory index
Pym Update Task — Edit an existing task's title, body, ASSIGNEE (assign it to a person — pass their @handle as assigneeHandle, or an identityId as assignee; null clears), or due date (epoch ms; null clears). The server load-merges — fields you omit are untouched. With a connected-agent (scoped) token the edit lands PROPOSED — a 202 with actionId — until a human approves it; undo restores the prior values. (Status is a separate tool, pym_update_task_status.)
Pym List Docs — List docs. Omit channelId for the cross-scope corpus (every active scope); pass channelId for one channel.
Pym Get Doc — A doc with its PROVENANCE: cross-domain links + the action(s) that created/touched it.
Pym Create Doc — Create a doc (one atomic action bundle). With a connected-agent (scoped) token the bundle lands PROPOSED — a 202 with actionId — until a human approves it in Pym. Optional links forge cross-domain edges in the SAME transaction (e.g. {toType:'contact',toId,rel:'about'}).
Pym Update Doc — Edit an existing doc's title and/or body (collaborative drafting). The server load-merges — fields you omit are untouched. With a connected-agent (scoped) token the edit lands PROPOSED — a 202 with actionId — and the human's approval card shows a body DIFF against the doc as you saw it; approval applies it, undo restores the prior body exactly.
Pym List Contacts — List CRM contacts. Omit channelId for the cross-scope corpus (every active scope); pass channelId for one channel.
Pym Get Contact — A contact with its PROVENANCE: cross-domain links + the action(s) that created/touched it.
Pym Create Contact — Create a CRM contact (one atomic action bundle). With a connected-agent (scoped) token the bundle lands PROPOSED — a 202 with actionId — until a human approves it in Pym. Optional links forge cross-domain edges in the SAME transaction (e.g. {toType:'message',toId,rel:'about'}).
Pym Update Contact — Edit an existing CRM contact's name, account, and/or fields (load-merged — omitted fields are untouched). With a connected-agent (scoped) token the edit lands PROPOSED (202 + actionId) until a human approves; undo restores the prior state exactly.
Pym Find Gaps — The gap-finder: CRM contacts (cross-scope) with NO linked OPEN task — the LEFT JOIN NULL. Surfaces promised-but-untracked accounts (e.g. 'promised early access, nobody filed the work').
Pym List Comments — An entity's ONE canonical comment stream (kind: task|doc|contact): every comment on the object, whatever channel it was typed from, chronological, each labeled with its origin channel. Visibility follows the OBJECT — anyone who can see the entity sees all of these. channelId is your vantage: the entity's home channel, or any channel it's shared into.
Pym Comment — Comment on an entity (kind: task|doc|contact) — ONE atomic bundle: a message + its `about` link to the object. The comment lives on the OBJECT (visible to everyone who can see it), not in the channel stream. With a connected-agent (scoped) token the comment lands PROPOSED — a 202 with actionId — until a human approves it in Pym.
Pym Get Thread — A message thread: the root message + its replies (parentId) + still-PROPOSED @pym bundles spawned from it (the in-thread proposal cards).
Pym Reply Message — Reply in a thread (pass parentId = the root message id). Mention @pym in the body to (re-)trigger an agent proposal. Goes through the action queue.
Showing the first 25 tools — full list and schemas: Directory API.
MCPBundles probed 45 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does 404: NOT_FOUND require?
404: NOT_FOUND may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.