portkey
Server Details
Read AI-gateway analytics, configs, virtual keys, workspaces and users; log request feedback.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
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
16 toolsportkey_create_feedbackCreate feedbackDestructiveInspect
WRITES a feedback record into the Portkey account, attached to a request/trace by trace_id. Use for logging a quality score (typically -10..10) with an optional weight (0..1) and metadata. Portkey: POST /feedback.
| Name | Required | Description | Default |
|---|---|---|---|
| value | Yes | Feedback score, typically -10..10. | |
| weight | No | Relative weight of this feedback, 0..1. | |
| metadata | No | Arbitrary metadata key/values. | |
| trace_id | Yes | The request/trace id to attach feedback to. |
portkey_get_analytics_graphGet analytics graphRead-onlyInspect
Get a time-series analytics graph for a single metric (cost, requests, tokens, latency, error-rate, cache-hit-rate, …) over a time window. Optionally scope by virtual keys, configs, or metadata. Portkey: GET /analytics/graphs/{metric}.
| Name | Required | Description | Default |
|---|---|---|---|
| metric | Yes | Which metric graph to return. | |
| configs | No | Comma-separated config slugs to scope the graph. | |
| metadata | No | JSON string of metadata key/values to scope the graph. | |
| total_units | No | Bucket size for the series, e.g. "day" or "hour". | |
| virtual_keys | No | Comma-separated virtual key slugs to scope the graph. | |
| time_of_generation_max | Yes | End of the window (ISO8601, format YYYY-MM-DDTHH:MM:SS±HH:MM). | |
| time_of_generation_min | Yes | Start of the window (ISO8601, format YYYY-MM-DDTHH:MM:SS±HH:MM). |
portkey_get_analytics_groupGet analytics groupRead-onlyInspect
Get grouped analytics (aggregated by models, users, or metadata) over a time window. Portkey: GET /analytics/groups/{group}.
| Name | Required | Description | Default |
|---|---|---|---|
| group | Yes | Dimension to group the analytics by. | |
| page_size | No | Number of records per page. Default 50. | |
| current_page | No | Page number (0-based) for pagination. Default 0. | |
| time_of_generation_max | Yes | End of the window (ISO8601, format YYYY-MM-DDTHH:MM:SS±HH:MM). | |
| time_of_generation_min | Yes | Start of the window (ISO8601, format YYYY-MM-DDTHH:MM:SS±HH:MM). |
portkey_get_api_keyGet API keyRead-onlyInspect
Get a single API key's metadata by id (the secret is never returned). Portkey: GET /api-keys/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The API key id. |
portkey_get_configGet configRead-onlyInspect
Get a single gateway config by slug (or id), including its routing rules. Portkey: GET /configs/{slug}.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The config slug or id. |
portkey_get_userGet userRead-onlyInspect
Get a single user by id. Portkey: GET /users/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The user id. |
portkey_get_virtual_keyGet virtual keyRead-onlyInspect
Get a single virtual key by slug, including its provider + limits. Portkey: GET /virtual-keys/{slug}.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The virtual key slug. |
portkey_get_workspaceGet workspaceRead-onlyInspect
Get a single workspace by slug/id. Portkey: GET /workspaces/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The workspace slug or id. |
portkey_list_api_keysList API keysRead-onlyInspect
List API keys in the organization/workspace (metadata only — secrets are never returned). Portkey: GET /api-keys.
| Name | Required | Description | Default |
|---|---|---|---|
| page_size | No | Number of records per page. Default 50. | |
| current_page | No | Page number (0-based) for pagination. Default 0. | |
| workspace_id | No | Scope keys to a workspace id/slug. |
portkey_list_audit_logsList audit logsRead-onlyInspect
List audit log entries (admin actions across the organization). Portkey: GET /audit-logs.
| Name | Required | Description | Default |
|---|---|---|---|
| page_size | No | Number of records per page. Default 50. | |
| current_page | No | Page number (0-based) for pagination. Default 0. |
portkey_list_configsList configsRead-onlyInspect
List gateway configs (routing/fallback/retry/cache rulesets applied to requests). Portkey: GET /configs.
| Name | Required | Description | Default |
|---|---|---|---|
| workspace_id | No | Scope configs to a workspace id/slug. |
portkey_list_user_invitesList user invitesRead-onlyInspect
List pending user invitations to the organization. Portkey: GET /user-invites.
| Name | Required | Description | Default |
|---|---|---|---|
| page_size | No | Number of records per page. Default 50. | |
| current_page | No | Page number (0-based) for pagination. Default 0. |
portkey_list_usersList usersRead-onlyInspect
List users in the organization. Filter by role or email. Portkey: GET /users.
| Name | Required | Description | Default |
|---|---|---|---|
| role | No | Filter users by role (e.g. admin, member). | |
| No | Filter users by email address. | ||
| page_size | No | Number of records per page. Default 50. | |
| current_page | No | Page number (0-based) for pagination. Default 0. |
portkey_list_virtual_keysList virtual keysRead-onlyInspect
List virtual keys (the aliases that map to provider credentials + budget/rate limits used in requests). Portkey: GET /virtual-keys.
| Name | Required | Description | Default |
|---|---|---|---|
| page_size | No | Number of records per page. Default 50. | |
| current_page | No | Page number (0-based) for pagination. Default 0. |
portkey_list_workspace_membersList workspace membersRead-onlyInspect
List members of a workspace (users + their roles). Portkey: GET /workspaces/{id}/members.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The workspace slug or id. | |
| page_size | No | Number of records per page. Default 50. | |
| current_page | No | Page number (0-based) for pagination. Default 0. |
portkey_list_workspacesList workspacesRead-onlyInspect
List workspaces in the organization. Portkey: GET /workspaces.
| Name | Required | Description | Default |
|---|---|---|---|
| page_size | No | Number of records per page. Default 50. | |
| current_page | No | Page number (0-based) for pagination. Default 0. |
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!