livespace-crm-mcp
by proAutomator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Server port. | 3020 |
| MCP_BIND_HOST | No | Bind address. | 127.0.0.1 |
| MCP_AUTH_TOKEN | No | Random bearer token of at least 32 bytes. Required on a non-loopback bind. | |
| LIVESPACE_API_KEY | Yes | API key for one Livespace user. | |
| MCP_ALLOWED_HOSTS | No | Host-header allowlist for DNS-rebinding protection. Required on a non-loopback bind. | |
| LIVESPACE_SUBDOMAIN | Yes | Account subdomain without protocol or .livespace.io. | |
| LIVESPACE_API_SECRET | Yes | API secret for one Livespace user. | |
| MCP_RATE_LIMIT_BURST | No | Per-principal request burst. | 30 |
| MCP_REQUEST_STATE_KEY | No | Secret of at least 32 bytes used to sign write confirmations. Required when authentication is enabled or the bind is not loopback. | |
| LIVESPACE_MCP_READ_ONLY | No | Set to true to remove and block all write tools. | false |
| MCP_MAX_QUEUED_REQUESTS | No | Admission limit for queued requests. | 16 |
| MCP_RATE_LIMIT_PER_MINUTE | No | Per-principal request rate. | 120 |
| MCP_MAX_CONCURRENT_REQUESTS | No | Admission limit for in-flight requests. | 8 |
| MCP_ALLOWED_ORIGIN_HOSTNAMES | No | Optional additional browser-origin hostnames. On a non-loopback bind it defaults to MCP_ALLOWED_HOSTS. | |
| MCP_REQUEST_INGRESS_TIMEOUT_MS | No | Absolute limit for admission queueing plus body upload, not tool execution. | 10000 |
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
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- 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/proAutomator/livespace-crm-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server