Agent MCP vs Scrivener MCP
A side-by-side look at the Agent MCP and Scrivener 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 MCP for coding agents work over a hosted endpoint; choose Scrivener MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Agent MCP when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OPENAI_API_KEY, AGENT_MCP_HOST, AGENT_MCP_PORT, AGENT_MCP_LOG_LEVEL, AGENT_MCP_PROJECT_DIR, AGENT_MCP_MAX_AGENTS. - You want tools like
create_agent, list_agents, terminate_agent.
Choose Scrivener MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Knowledge & Memory |
| Quality signal | 60/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | OPENAI_API_KEYAGENT_MCP_HOSTAGENT_MCP_PORTAGENT_MCP_LOG_LEVELAGENT_MCP_PROJECT_DIRAGENT_MCP_MAX_AGENTS | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,303 | 67 |
| Directory activity | 5 views 0 installs 0 upvotes | 18 views 12 installs 6 upvotes |
| Tools | 12 | Not listed |
| Full listing | View Agent MCP | View Scrivener MCP |
Tools & capabilities
Agent MCP tools 12
create_agentlist_agentsterminate_agentassign_taskview_tasksupdate_task_statusask_project_ragupdate_project_contextview_project_contextsend_agent_messagebroadcast_messagerequest_assistance
Scrivener MCP tools
No tool names declared yet. Check the project README from 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 MCP
{
"mcpServers": {
"rinadelph-agent-mcp": {
"url": "http://localhost:8000/mcp"
}
}
}
Scrivener MCP
{
"mcpServers": {
"writerslogic-scrivener-mcp": {
"command": "npx",
"args": [
"-y",
"scrivener-setup"
]
}
}
}
Frequently asked questions
Agent MCP is categorized under Coding Agents and uses a remote HTTP/SSE transport. Scrivener MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Agent MCP for coding agents work and Scrivener MCP for knowledge & memory.
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 MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Scrivener MCP is listed as free. Auth: no auth required. 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 rinadelph-agent-mcp and writerslogic-scrivener-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent MCP has a quality signal of 60/100 (Good) with 5 views, 0 installs and 1,303 GitHub stars. Scrivener MCP has 61/100 (Good) with 18 views, 12 installs and 67 GitHub stars.