Skip to main content
Glama

MCP Integration Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JIRA_URLNoe.g., https://your-domain.atlassian.net
JIRA_EMAILNoAtlassian account email
SUPABASE_URLNoYour Supabase project URL
CONFLUENCE_URLNoe.g., https://your-domain.atlassian.net/wiki
JIRA_API_TOKENNoAPI token generated from Atlassian account
CONFLUENCE_EMAILNoAtlassian account email
SUPABASE_ANON_KEYNoKey to access your Supabase (start with ANON; use Service Role only with proper RLS)
VITE_SUPABASE_URLNoYour Supabase project URL (backward-compatible name)
CONFLUENCE_API_TOKENNoAPI token generated from Atlassian account
VITE_SUPABASE_ANON_KEYNoKey to access your Supabase (backward-compatible name)
SALESFORCE_ACCESS_TOKENNoOAuth/Bearer token with appropriate scopes
SALESFORCE_INSTANCE_URLNoe.g., https://your-domain.my.salesforce.com
SUPABASE_SERVICE_ROLE_KEYNoService role key to access your Supabase (use only with proper RLS)

Schema

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Tools

Functions exposed to the LLM to take actions

NameDescription

No tools

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/henrymclane09/MCPtest'

If you have feedback or need assistance with the MCP directory API, please join our Discord server