location-history-mcp-server
by lucas-1000
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABASE_URL | Yes | PostgreSQL connection URL with PostGIS extension. Example: postgresql://user:pass@/health_data?host=/cloudsql/PROJECT:REGION:INSTANCE | |
| DEFAULT_USER_ID | No | Default user id (email) for the location tracker. Used if no user id is specified in requests. | lucashanson132@gmail.com |
| GOOGLE_PLACES_API_KEY | No | Optional Google Places API key for automatic place name resolution. |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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/lucas-1000/location-history-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server