try
Server Details
Create guides as MCP servers to instruct coding agents to use your software (library, API, etc).
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
13 toolsadd_data_sourceInspect
Add a new data source to a project
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL of the data source | |
| type | Yes | The type of data source | |
| session_id | Yes | The anonymous session ID | |
| project_slug | Yes | The slug of the project to add the data source to |
add_toolInspect
Add a new tool/step to a project
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The unique name of the tool (used as identifier) | |
| tool_type | No | The type of tool (step, builtin, tip) | step |
| is_enabled | No | Whether the tool is enabled | |
| session_id | Yes | The anonymous session ID | |
| step_order | No | The order of this step in the project workflow | |
| description | No | Description of what the tool does | |
| tool_schema | No | JSON schema for tool parameters | |
| display_name | Yes | The human-readable display name of the tool | |
| project_slug | Yes | The slug of the project to add the tool to | |
| response_template | No | Markdown template for tool response |
create_projectInspect
Create a new project in the anonymous session
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The display name of the project | |
| slug | Yes | The URL slug for the project (used in URLs) | |
| is_public | No | Whether the project is public or private | |
| session_id | Yes | The anonymous session ID | |
| overview_content | No | Markdown content for the project overview |
create_sessionInspect
Create a new anonymous session for managing projects
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
delete_data_sourceInspect
Delete a data source from a project
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | The anonymous session ID | |
| data_source_id | Yes | The ID of the data source to delete |
delete_projectInspect
Delete a project from the anonymous session
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | The anonymous session ID | |
| project_slug | Yes | The slug of the project to delete |
delete_toolInspect
Delete a tool from a project
| Name | Required | Description | Default |
|---|---|---|---|
| tool_id | Yes | The ID of the tool to delete | |
| session_id | Yes | The anonymous session ID |
get_project_detailsInspect
Get detailed information about a specific project in the session
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | The anonymous session ID | |
| project_slug | Yes | The slug of the project to get details for |
list_projectsInspect
List all projects in the anonymous session
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | The anonymous session ID |
reorder_stepsInspect
Reorder tools/steps in a project
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | The anonymous session ID | |
| tool_orders | Yes | Array of tool IDs and their new step orders | |
| project_slug | Yes | The slug of the project to reorder tools in |
toggle_toolInspect
Toggle a tool's enabled/disabled state
| Name | Required | Description | Default |
|---|---|---|---|
| tool_id | Yes | The ID of the tool to toggle | |
| session_id | Yes | The anonymous session ID |
update_projectInspect
Update an existing project in the anonymous session
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | The display name of the project | |
| slug | No | The URL slug for the project (used in URLs) | |
| is_public | No | Whether the project is public or private | |
| session_id | Yes | The anonymous session ID | |
| project_slug | Yes | The slug of the project to update | |
| overview_content | No | Markdown content for the project overview |
update_toolInspect
Update an existing tool
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | The unique name of the tool (used as identifier) | |
| tool_id | Yes | The ID of the tool to update | |
| tool_type | No | The type of tool (step, builtin, tip) | |
| is_enabled | No | Whether the tool is enabled | |
| session_id | Yes | The anonymous session ID | |
| step_order | No | The order of this step in the project workflow | |
| description | No | Description of what the tool does | |
| tool_schema | No | JSON schema for tool parameters | |
| display_name | No | The human-readable display name of the tool | |
| response_template | No | Markdown template for tool response |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail — every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control — enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management — store and rotate API keys and OAuth tokens in one place
Change alerts — get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption — public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics — see which tools are being used most, helping you prioritize development and documentation
Direct user feedback — users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!