GPS
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GPSlook up Dana's team and role"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GPS - Global Positioning System MCP Server
A read-only caching tier that gives agents and humans sub-millisecond access to org and engineering data. GPS materializes people, teams, issues, features, release schedules, component mappings, and governance documents into a SQLite database and serves them over MCP — optimized for high-frequency agent queries with zero upstream latency.
Why GPS exists: Agents need fast, reliable access to org and engineering data. Querying live APIs (Jira, Confluence, HR systems) on every turn is slow, rate-limited, and fragile. GPS pre-materializes everything into a single SQLite file, opens it read-only, and serves structured results in microseconds. No auth, no rate limits, no network dependencies at query time.
5-Minute Quickstart
# 1. Clone and enter
git clone https://github.com/YOUR-ORG/gps.git && cd gps
# 2. Install uv (if needed)
curl -LsSf https://astral.sh/uv/install.sh | sh
# 3. Copy env and customize org mapping
cp .env.example .env
# 4. Place your data files in data/
# - An XLSX org spreadsheet (any .xlsx file)
# - CSV exports: issues, features, releases, etc.
# (Example data ships in data/acme-* for testing)
# 5. Build the database
uv run scripts/build_db.py --force
# 6. Run tests
scripts/test.sh
# 7. Start the MCP server
uv run mcp_server.py # stdio (for Claude Code / ACP)
uv run mcp_server.py --http # HTTP on :8000 (for shared deployments)Related MCP server: standards-mcp
Architecture
graph TD
subgraph Sources["Data Sources (refreshed periodically)"]
XLSX["XLSX\nOrg Spreadsheet"]
CSV["CSV\nIssues, Features,\nReleases"]
GOV["Markdown / PDF\nGovernance Docs"]
end
ETL["build_db.py\n(ETL Pipeline)"]
DB[("gps.db\nSQLite — read-only cache\nsub-ms queries")]
subgraph Server["MCP Server (no auth required)"]
MCP["mcp_server.py"]
TOOLS["9 Tools\nlookup_person, search_issues,\nrelease_risk_summary, ..."]
RES["2 Resources\ngps://schema\ngps://catalog"]
end
subgraph Clients["Clients"]
ACP["ACP Sessions\n(stdio, every pod)"]
CC["Claude Code\n(stdio, local)"]
HTTP["Shared Deployment\n(HTTP :8000)"]
end
XLSX --> ETL
CSV --> ETL
GOV --> ETL
ETL --> DB
DB --> MCP
MCP --- TOOLS
MCP --- RES
MCP -->|stdio| ACP
MCP -->|stdio| CC
MCP -->|streamable-http| HTTP
style DB fill:#e8f4f8,stroke:#2196F3,stroke-width:2px
style MCP fill:#fff3e0,stroke:#FF9800,stroke-width:2px
style ETL fill:#f3e5f5,stroke:#9C27B0,stroke-width:2pxHow it works
ETL pipeline (
scripts/build_db.py) loads all sources into a single SQLite database — runs periodically, not per-queryMCP server (
mcp_server.py) opens the database read-only with mmap, 64MB cache, and memory-backed temp store — tuned for agent query patternsNo auth required — the database contains read-only organizational data; agents connect directly via stdio or HTTP
The LLM never touches upstream data sources directly — clean security boundary
Client-Server Interaction
sequenceDiagram
participant Agent as Agent / Human
participant MCP as GPS MCP Server
participant DB as gps.db (SQLite)
Note over DB: Pre-built by ETL pipeline<br/>Opened read-only at startup
Agent->>MCP: tool call: lookup_person(name="Dana")
MCP->>DB: SELECT ... FROM person WHERE name LIKE '%Dana%'
DB-->>MCP: rows (sub-ms)
MCP-->>Agent: JSON {results: [...], count: 1}
Agent->>MCP: tool call: search_issues(status="In Progress", component="api")
MCP->>DB: SELECT ... FROM jira_issue WHERE status LIKE ... AND EXISTS(...)
DB-->>MCP: rows (sub-ms)
MCP-->>Agent: JSON {issues: [...], count: 12}
Agent->>MCP: tool call: release_risk_summary()
MCP->>DB: SELECT ... FROM release_milestone
MCP->>DB: SELECT ... FROM feature_release
MCP->>DB: SELECT ... FROM feature WHERE feature_id IN (...)
DB-->>MCP: rows
MCP-->>Agent: JSON {releases: [...], assessed_on: "2026-03-20"}
Agent->>MCP: resource: gps://schema
MCP->>DB: SELECT sql FROM sqlite_master
DB-->>MCP: DDL statements
MCP-->>Agent: Full schema with row counts
Note over Agent,DB: All queries are read-only<br/>No writes, no auth, no rate limitsMCP Tools
Tool | Description |
| Find people by name, email, or user ID (partial match) |
| List all members of a scrum team with roles and components |
| Search issues by status, priority, assignee, component, label, or keyword |
| Get feature details: progress, RICE score, releases, components, teams |
| Assess release risk — flags features under 80% complete near milestones |
| List governance documents with table of contents |
| Retrieve full governance document content by ID |
| Retrieve a specific section by fuzzy heading match |
| Return GPS version and build metadata |
MCP Resources
URI | Description |
| Full database DDL with row counts — agents should read this first |
| Data source inventory (DATA_CATALOG.yaml) |
Wiring GPS into ACP Sessions
GPS runs as a sidecar MCP in every ACP pod — no auth needed. The recommended approach is adding it to the runner's managed settings:
{
"mcpServers": {
"gps": {
"command": "uv",
"args": ["run", "--script", "/app/gps/mcp_server.py"]
}
}
}Bake mcp_server.py + data/gps.db + VERSION into the runner image or mount via shared volume. For init container and HTTP sidecar patterns, see docs/DEPLOYMENT.md.
Project Structure
mcp_server.py MCP server (stdio default, --http for HTTP)
scripts/
build_db.py ETL pipeline — materializes gps.db from source files
test.sh Test suite (lint, build, integrity, schema diff)
data/
acme-* Example data files (tracked)
*.csv, *.xlsx, *.db User data files (gitignored)
deploy/
deploy.sh Build, apply, status, logs automation
k8s/ Kubernetes/OpenShift manifests (kustomize)
docs/
adr/ Architecture Decision Records
DEPLOYMENT.md Deployment guide (local, container, k8s, ACP)
CUSTOMIZATION.md Customization guide (env vars, adding sources)
SCHEMA.md Database schema reference (ER diagram, tables, views)
governance/ Policy documents (auto-loaded into DB)
Containerfile Container image build
.env.example Configuration template
.mcp.json Claude Code MCP server configConfiguration
GPS is configured via environment variables (see .env.example):
GPS_TAB_ORG_MAP— JSON mapping of XLSX tab names to[org_key, org_name]pairsGPS_JIRA_SCRUM_REF_TAB— XLSX tab name for Jira-to-Scrum-team mappings
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ambient-code/gps'
If you have feedback or need assistance with the MCP directory API, please join our Discord server