Agent Comms vs Artifyde MCP
A side-by-side look at the Agent Comms and Artifyde MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agent Comms for communication work as a local process; choose Artifyde MCP for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Agent Comms when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
Choose Artifyde MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ARTIFYDE_TOKEN, ARTIFYDE_API_KEY, ARTIFYDE_URL. - You want tools like
push_artifact, pull_artifact, get_page.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 49/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | ARTIFYDE_TOKENARTIFYDE_API_KEYARTIFYDE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 34 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 14 |
| Full listing | View Agent Comms | View Artifyde MCP |
Tools & capabilities
Agent Comms tools
No tool names declared yet. Check the project README from the listing page.
Artifyde MCP tools 14
push_artifactPublish HTML → a stable view URL. Re-push to a `page_id` to add a version.pull_artifactDownload a version's byte-exact HTML.get_pagePage metadata + version history.list_pagesYour pages, with version/comment counts (filter by archived / query).rename_pageSet a page's display title.archive_pageHide/restore a page (read-only when archived).get_shareA page's visibility + invited-email list.set_visibilityMake a page `public` or `private`.share_pageInvite / revoke an email on a private page.list_commentsRead a page's comment threads.create_commentPost a comment (or reply) on a version.list_shelvesManage gallery groupings.- +2 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Agent Comms
{
"mcpServers": {
"agent-comms": {
"command": "npx",
"args": [
"-y",
"agent-comms"
]
}
}
}
Artifyde MCP
{
"mcpServers": {
"artifyde-mcp": {
"command": "npx",
"args": [
"-y",
"artifyde-mcp"
],
"env": {
"ARTIFYDE_TOKEN": "YOUR_ARTIFYDE_TOKEN_HERE",
"ARTIFYDE_API_KEY": "YOUR_ARTIFYDE_API_KEY_HERE",
"ARTIFYDE_URL": "YOUR_ARTIFYDE_URL_HERE"
}
}
}
}
Frequently asked questions
Agent Comms is categorized under Communication and uses a local stdio subprocess. Artifyde MCP belongs to Communication and uses a local stdio subprocess. Pick Agent Comms for communication work and Artifyde MCP for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Agent Comms has no declared pricing — check the project's own site. Artifyde MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add agent-comms and artifyde-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Comms has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 34 GitHub stars. Artifyde MCP has 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars.