Flip Database MCP
by mhummel94
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JWT_SECRET | Yes | A long random string for JWT signing | |
| OAUTH_ISSUER | Yes | Your deployed Railway URL, e.g. https://flip-database-mcp-production.up.railway.app | |
| MCP_AUTH_TOKEN | Yes | A random string for static-token authentication fallback | |
| FLIP_SUPABASE_URL | Yes | Your flip-tracking Supabase project → Settings → API URL | |
| FLIP_DB_READONLY_URL | Yes | Postgres connection string using the flip_readonly role, e.g. postgresql://flip_readonly:YOUR_PASSWORD@YOUR_PROJECT_HOST:5432/postgres | |
| FLIP_SUPABASE_SERVICE_KEY | Yes | Your flip-tracking Supabase project legacy service_role key (not the new sb_secret_... format) |
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
ActivitySlowing
ResponsivenessNo issues