Raptee Ops Agent
by BASILAHAMED
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port the MCP server listens on (passed as PORT=3301). Serves the MCP endpoint at /mcp and a health check at /health. | 3301 |
| SEED | No | Set to 1 to seed the SQLite database with example data (~7 owners/bikes, mixed ticket statuses, staggered test-ride/service slots, 14 days of sales, 3 unconverted leads, showroom inventory, and 2 RSA calls). Passed as SEED=1. | |
| DB_PATH | No | Path to the SQLite database file used by the server (passed as DB_PATH=./raptee-ops.db). On Vercel the DB is written to /tmp and re-seeded on every cold start. | ./raptee-ops.db |
| MCP_TOKEN | Yes | Bearer token used to authenticate requests to the MCP server (passed as MCP_TOKEN=change-me). This must match the MCP_TOKEN configured in the simulated Alexa+ web app's .env.local. |
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