Mira MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TOKEN | Yes | Bearer token required to authenticate to the MCP server (sent as `Authorization: Bearer <MCP_TOKEN>`). | |
| APPROVAL_TOKEN | Yes | Separate token used for the human approval route (`POST /approvals/:id`). The agent never sees this token. | |
| BASE44_BRIDGE_URL | No | Optional. URL of a hosted Kinetic Home household bridge. Requires HTTPS. The bridge is off unless configured. | |
| BASE44_HOUSEHOLD_ID | No | Optional. Hosted household ID used by the bridge. Must be set server-side, never in a browser or source. | |
| BASE44_APP_USER_TOKEN | No | Optional. App user token for the hosted household bridge. Must be set server-side, never in a browser or source. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
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 | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues