Code Context vs MCP Sqlite
A side-by-side look at the Code Context and MCP Sqlite MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Code Context for databases work as a local process; choose MCP Sqlite for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Code Context when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
Choose MCP Sqlite when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
db_info, query, list_tables.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 47/100 · Fair | 65/100 · Great |
| 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 | 32 | 131 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | 8 |
| Full listing | View Code Context | View MCP Sqlite |
Tools & capabilities
Code Context tools
No tool names declared yet. Check the project README from the listing page.
MCP Sqlite tools 8
db_infoGet information about the SQLite database including path, existence, size, and table countqueryExecute a raw SQL query against the database with optional parameter valueslist_tablesList all user tables in the SQLite database (excludes system tables)get_table_schemaGet the schema information for a specific table including column detailscreate_recordInsert a new record into a table with specified dataread_recordsRead records from a table with optional conditions, limit, and offsetupdate_recordsUpdate records in a table based on specified conditionsdelete_recordsDelete records from a table based on specified conditions
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.
Code Context
{
"mcpServers": {
"code-context": {
"command": "npx",
"args": [
"-y",
"@infino-ai/code-context"
]
}
}
}
MCP Sqlite
{
"mcpServers": {
"jparkerweb-mcp-sqlite": {
"command": "npx",
"args": [
"-y",
"mcp-sqlite"
]
}
}
}
Frequently asked questions
Code Context is categorized under Databases and uses a local stdio subprocess. MCP Sqlite belongs to Databases and uses a local stdio subprocess. Pick Code Context for databases work and MCP Sqlite for databases.
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.
Code Context has no declared pricing — check the project's own site. MCP Sqlite 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 code-context and jparkerweb-mcp-sqlite as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Code Context has a quality signal of 47/100 (Fair) with 0 views, 0 installs and 32 GitHub stars. MCP Sqlite has 65/100 (Great) with 5 views, 0 installs and 131 GitHub stars.