Contextful vs Codebase Context
A side-by-side look at the Contextful and Codebase Context MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Contextful for knowledge & memory work as a local process; choose Codebase Context 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 Contextful when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
Choose Codebase Context 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.
- You want tools like
search_codebase, get_team_patterns, get_symbol_references.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 41/100 · Fair | 64/100 · Good |
| 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 | 5 | 65 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 10 |
| Full listing | View Contextful | View Codebase Context |
Tools & capabilities
Contextful tools
No tool names declared yet. Check the project README from the listing page.
Codebase Context tools 10
search_codebaseHybrid search + decision card when `intent="edit"get_team_patternsPattern frequencies, golden files, conflict detectionget_symbol_referencesConcrete references to a symbol (count + snippets)rememberRecord a convention, decision, gotcha, or failureget_memoryQuery team memory with confidence decay scoringget_codebase_metadataProject structure, frameworks, dependenciesget_style_guideStyle guide rules for the current projectdetect_circular_dependenciesImport cycles between filesrefresh_indexFull or incremental re-index + git memory extractionget_indexing_statusProgress and stats for the current index
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.
Contextful
{
"mcpServers": {
"contextful": {
"command": "npx",
"args": [
"-y",
"@inferensys/contextful"
]
}
}
}
Codebase Context
{
"mcpServers": {
"patricksys-codebase-context": {
"command": "npx",
"args": [
"-y",
"codebase-context"
]
}
}
}
Frequently asked questions
Contextful is categorized under Knowledge & Memory and uses a local stdio subprocess. Codebase Context belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Contextful for knowledge & memory work and Codebase Context 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.
Contextful has no declared pricing — check the project's own site. Codebase Context 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 contextful and patricksys-codebase-context as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Contextful has a quality signal of 41/100 (Fair) with 2 views, 0 installs and 5 GitHub stars. Codebase Context has 64/100 (Good) with 2 views, 0 installs and 65 GitHub stars.