Skip to main content
Glama
MCP Connect Starter

MCP Connect Starter

by cdtalley

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_CONNECT_DB_PATHNoSQLite database path../data/demo.sqlite3
MCP_CONNECT_DOCS_DIRNoKnowledge-base folder../data/docs
MCP_CONNECT_HTTP_HOSTNoStreamable HTTP bind host.127.0.0.1
MCP_CONNECT_HTTP_PORTNoStreamable HTTP bind port.8080
MCP_CONNECT_CRM_FIXTURENoMock CRM fixture path../data/crm_mock.json
MCP_CONNECT_SCOPES_FILENoTool policy file../config/scopes.yaml
MCP_CONNECT_SQL_MAX_ROWSNoMax rows per SQL query.200
MCP_CONNECT_ALLOWED_TOOLSNoOptional hard tool-name allowlist. Unset means all tools are allowed.
MCP_CONNECT_SQL_TIMEOUT_SNoPer-query timeout in seconds.5
MCP_CONNECT_AUDIT_LOG_FILENoAlso append audit JSON lines here. Unset means stderr only.
MCP_CONNECT_GRANTED_SCOPESNoScopes 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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 ? placeholders in sql and pass values via params rather than formatting them into the query text. Results are capped at MCP_CONNECT_SQL_MAX_ROWS rows (see truncated in the response).

search_docsB

Search the bundled markdown knowledge base and return the best-matching documents.

read_docB

Read one markdown document by the path returned from search_docs.

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 crm:write scope to demonstrate least-privilege-by-default.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 8 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness3/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues