Britive MCP Server
Officialby britive
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHONPATH | No | Set the Python path to the mcp-server directory (repository). | |
| BRITIVE_EMAIL | No | The Britive email of the person you want the MCP server to impersonate (for on-behalf-of functionality). | |
| BRITIVE_TENANT | No | Your tenant on Britive. Do not use the entire FQDN for the subdomain. For example, for https://super-customer.test.aws.britive-corp.com, use super-customer.test.aws as a tenant subdomain. | |
| BRITIVE_STATIC_TOKEN | No | Static token created from Britive UI for API authentication. |
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 | |
Latest Blog Posts
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/britive/mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server