MCP Integration Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | No | e.g., https://your-domain.atlassian.net | |
| JIRA_EMAIL | No | Atlassian account email | |
| SUPABASE_URL | No | Your Supabase project URL | |
| CONFLUENCE_URL | No | e.g., https://your-domain.atlassian.net/wiki | |
| JIRA_API_TOKEN | No | API token generated from Atlassian account | |
| CONFLUENCE_EMAIL | No | Atlassian account email | |
| SUPABASE_ANON_KEY | No | Key to access your Supabase (start with ANON; use Service Role only with proper RLS) | |
| VITE_SUPABASE_URL | No | Your Supabase project URL (backward-compatible name) | |
| CONFLUENCE_API_TOKEN | No | API token generated from Atlassian account | |
| VITE_SUPABASE_ANON_KEY | No | Key to access your Supabase (backward-compatible name) | |
| SALESFORCE_ACCESS_TOKEN | No | OAuth/Bearer token with appropriate scopes | |
| SALESFORCE_INSTANCE_URL | No | e.g., https://your-domain.my.salesforce.com | |
| SUPABASE_SERVICE_ROLE_KEY | No | Service role key to access your Supabase (use only with proper RLS) |
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
ActivityInactive
ResponsivenessNo issues