Innernet vs Cortex
A side-by-side look at the Innernet and Cortex MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
I
InnernetKnowledge & MemoryOne memory for every AI tool, kept current by netti: projects, personal memory and tasks over MCP.36FairAuth: oauth 2.0Verdict: choose Innernet for knowledge & memory work; choose Cortex for knowledge & memory over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
IChoose Innernet when
- You need dedicated capabilities in the Knowledge & Memory domain.
- Its auth model fits you: OAuth 2.0.
Choose Cortex when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
CORTEX_ACCESS_TOKEN, CORTEX_MCP_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | I Innernet | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 36/100 · Fair | 40/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | CORTEX_ACCESS_TOKENCORTEX_MCP_URL |
| Verified owner |
Tools & capabilities
Innernet tools
No tool names declared yet. Check the project README from the listing page.
Cortex 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.
Innernet
No confirmed install command for Innernet yet — follow the setup steps linked from its listing page rather than a guessed package name.
Cortex
{
"mcpServers": {
"cortex-5": {
"url": "https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp"
}
}
}
Frequently asked questions
Innernet is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. Cortex belongs to Knowledge & Memory and uses a remote HTTP/SSE transport. Pick Innernet for knowledge & memory work and Cortex 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. Innernet has no confirmed install command yet — follow its own setup instructions.
Innernet is listed as free. Auth: oauth 2.0. Cortex 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 innernet-2 and cortex-5 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Innernet has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Cortex has 40/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.