Janusmcp vs Metatool App
A side-by-side look at the Janusmcp and Metatool App MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Janusmcp for aggregators work as a local process; choose Metatool App for aggregators as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Janusmcp when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- You want tools like
janus_list_accounts, janus_login, janus_use_account.
Choose Metatool App when
- You need dedicated capabilities in the Aggregators 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 | Aggregators | Aggregators |
| Quality signal | 64/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 9 | 2,722 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Janusmcp | View Metatool App |
Tools & capabilities
Janusmcp tools 5
janus_list_accountsList configured accounts/services and which is active for this session.janus_loginStart an OAuth login for <provider> in your browser and store the token as <name>. The token is captured locally and saved to the OS keychain — it never passes through this chat. Afterwards reference it from an account env as "oauth:<name>". Built-in providers: github, google, supabase.janus_use_accountSet the active account/identity. Reloads upstream tools and notifies the client. scope: 'session' or 'global' (defaults to the broker bindingMode).janus_whoamiReturn the active account for this session and how it was resolved.janus_with_accountRun a single tool call on another account WITHOUT changing the active account. Omit 'tool' to first list that account's available tools.
Metatool App 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.
Janusmcp
{
"mcpServers": {
"janusmcp": {
"command": "npx",
"args": [
"-y",
"@bayway/janusmcp"
]
}
}
}
Metatool App
{
"mcpServers": {
"metatool-ai-metatool-app": {
"command": "uvx",
"args": [
"mcp-hn"
]
}
}
}
Frequently asked questions
Janusmcp is categorized under Aggregators and uses a local stdio subprocess. Metatool App belongs to Aggregators and uses a local stdio subprocess. Pick Janusmcp for aggregators work and Metatool App for aggregators.
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.
Janusmcp has no declared pricing — check the project's own site. Metatool App 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 janusmcp and metatool-ai-metatool-app as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Janusmcp has a quality signal of 64/100 (Good) with 1 views, 0 installs and 9 GitHub stars. Metatool App has 45/100 (Fair) with 3 views, 0 installs and 2,722 GitHub stars.