MCP Connect Starter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_CONNECT_DB_PATH | No | SQLite database path. | ./data/demo.sqlite3 |
| MCP_CONNECT_DOCS_DIR | No | Knowledge-base folder. | ./data/docs |
| MCP_CONNECT_HTTP_HOST | No | Streamable HTTP bind host. | 127.0.0.1 |
| MCP_CONNECT_HTTP_PORT | No | Streamable HTTP bind port. | 8080 |
| MCP_CONNECT_CRM_FIXTURE | No | Mock CRM fixture path. | ./data/crm_mock.json |
| MCP_CONNECT_SCOPES_FILE | No | Tool policy file. | ./config/scopes.yaml |
| MCP_CONNECT_SQL_MAX_ROWS | No | Max rows per SQL query. | 200 |
| MCP_CONNECT_ALLOWED_TOOLS | No | Optional hard tool-name allowlist. Unset means all tools are allowed. | |
| MCP_CONNECT_SQL_TIMEOUT_S | No | Per-query timeout in seconds. | 5 |
| MCP_CONNECT_AUDIT_LOG_FILE | No | Also append audit JSON lines here. Unset means stderr only. | |
| MCP_CONNECT_GRANTED_SCOPES | No | Scopes this deployment holds. | data:read,docs:read,crm:read |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
MCP Connect Starter exposes three connectors, all read-only unless the deployment explicitly grants a write scope: sql_query / list_sql_tables over a sample customers/orders/deals SQLite database, search_docs / read_doc over a markdown knowledge base, and list_tickets / get_ticket / search_contacts over a mock CRM. Call list_sql_tables before writing ad hoc SQL, and search_docs before read_doc. Every tool call is audit logged and PII (emails, phone numbers, SSNs, card numbers) is redacted from tool output.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sql_tablesA | List the tables and columns available in the demo SQL database. |
| sql_queryA | Run a read-only SQL query against the demo database. Only a single SELECT or WITH...SELECT statement is allowed; writes,
DDL, and multi-statement payloads are rejected before they reach
SQLite. Use |
| search_docsB | Search the bundled markdown knowledge base and return the best-matching documents. |
| read_docB | Read one markdown document by the |
| list_ticketsA | List support tickets, newest first, optionally filtered by status (open/pending/closed). |
| get_ticketB | Get one support ticket by id, including its comment thread. |
| search_contactsC | Search CRM contacts by name, email, or company. |
| add_ticket_commentA | Add a comment to a ticket and return it updated. Disabled by default (see config/scopes.yaml) -- this is the one
write-capable tool in the starter, gated behind the |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a clearly distinct resource and action: SQL introspection/query, document search/read, ticket listing/retrieval/commenting, and contact search. There is no meaningful overlap that would cause an agent to select the wrong tool.
Tool names are consistently snake_case and mostly follow a verb_noun pattern such as list_tickets, get_ticket, search_docs, and add_ticket_comment. sql_query is a minor deviation from the verb_noun convention but remains clear.
Eight tools are well within a sensible range for a starter server demonstrating multiple integrations. Each tool has a specific role and the set does not feel bloated or thin.
The SQL and document surfaces cover their intended read-only workflows, and tickets support listing, retrieval, and commenting. However, ticket lifecycle operations like create/update/close are absent, and contacts only support search with no get/create/update tools.