Serverless edge control plane to discover, route and monetize 14,982+ MCP tools.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Compact snapshot of the MetaMesh gateway: active tool count, top categories, payment/billing status, last discovery. Best first call for context.
This tool takes no arguments.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Compact snapshot of the MetaMesh gateway: active tool count, top categories, payment/billing status, last discovery. Best first call for context.
No arguments.
{
"type": "object",
"properties": {}
}Control/observability: status of the registry discovery engine (active tools, last run, pages fetched).
No arguments.
{
"type": "object",
"properties": {}
}Gateway health: database connectivity, payment configuration and feature flags.
No arguments.
{
"type": "object",
"properties": {}
}Usage analytics: total tools, calls, success rate and recent error counts. Read-only.
No arguments.
{
"type": "object",
"properties": {}
}Search the catalog of 13k+ MCP tools by keyword. Returns concise matches (name, category, description). Use this instead of listing all tools.
| Argument | Type | Description |
|---|---|---|
| q* | string | Search query, e.g. "github", "database", "email" |
| limit | number | Max results (default 10, max 50) |
{
"type": "object",
"required": [
"q"
],
"properties": {
"q": {
"type": "string",
"description": "Search query, e.g. \"github\", \"database\", \"email\""
},
"limit": {
"type": "number",
"description": "Max results (default 10, max 50)"
}
}
}Detailed info for a specific catalog tool: description, category, trust/security score, state, source.
| Argument | Type | Description |
|---|---|---|
| name* | string | Exact tool name |
{
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "Exact tool name"
}
}
}This will get the account info for the logged in Stripe account.
No arguments.
{
"type": "object",
"properties": {}
}Search the Stripe documentation for the given question and language. It takes two arguments: - question (str): The user question to search an answer for in the Stripe documentati…
| Argument | Type | Description |
|---|---|---|
| language | string | The programming language to search for in the documentation. |
| question* | string | The user question about integrating with Stripe will be used to search the documentation. |
| search_only_api_ref | boolean | When set to true, search only in the Stripe API reference documentation instead of the full documentation set. Use true when users need specific API implementation details, code examples, or parameter references. Use false (default) for conceptual explanations, best practices, integration guides, or troubleshooting help. |
{
"type": "object",
"required": [
"question"
],
"properties": {
"language": {
"enum": [
"dotnet",
"go",
"java",
"node",
"php",
"ruby",
"python",
"curl"
],
"type": "string",
"description": "The programming language to search for in the documentation."
},
"question": {
"type": "string",
"maxLength": 1000,
"description": "The user question about integrating with Stripe will be used to search the documentation."
},
"search_only_api_ref": {
"type": "boolean",
"description": "When set to true, search only in the Stripe API reference documentation instead of the full documentation set. Use true when users need specific API implementation details, code examples, or parameter references. Use false (default) for conceptual explanations, best practices, integration guides, or troubleshooting help."
}
}
}Share feedback about Stripe's products. Submit when the user gives product feedback or you observe something concrete that worked or failed. Do not report model behavior, the use…
| Argument | Type | Description |
|---|---|---|
| actor | string | Who decided to submit: human or agent. Defaults to agent. |
| context* | string | What the user was trying to accomplish. Do not include sensitive business information. |
| message* | string | What broke or worked, concrete and specific. At least 5 words. |
| sentiment* | string | positive, negative, or neutral |
| feature_area | string | Product area this feedback is about. |
{
"type": "object",
"required": [
"sentiment",
"message",
"context"
],
"properties": {
"actor": {
"enum": [
"human",
"agent"
],
"type": "string",
"description": "Who decided to submit: human or agent. Defaults to agent."
},
"context": {
"type": "string",
"maxLength": 2000,
"minLength": 20,
"description": "What the user was trying to accomplish. Do not include sensitive business information."
},
"message": {
"type": "string",
"maxLength": 2000,
"minLength": 20,
"description": "What broke or worked, concrete and specific. At least 5 words."
},
"sentiment": {
"enum": [
"positive",
"negative",
"neutral"
],
"type": "string",
"description": "positive, negative, or neutral"
},
"feature_area": {
"enum": [
"payments",
"connect",
"subscriptions",
"billing",
"payouts",
"reporting",
"invoicing",
"invoices",
"checkout",
"tax",
"radar",
"issuing",
"terminal",
"treasury",
"capital",
"docs",
"webhooks",
"cli",
"dashboard",
"crypto",
"stablecoins",
"managed-payments",
"mcp",
"identity",
"skills",
"apps",
"other"
],
"type": "string",
"description": "Product area this feedback is about."
}
}
}This tool is for analyzing Stripe Sigma and Metrics data (e.g. about revenue, charges, products, invoices, subscriptions, disputes, transactions, tax tables, payments etc) and run…
| Argument | Type | Description |
|---|---|---|
| intent* | string | The intent of the tool call. |
| params | object | The parameters for the tool call. Required parameters depend on the intent. |
{
"type": "object",
"required": [
"intent"
],
"properties": {
"intent": {
"enum": [
"execute_query_run",
"retrieve_query_run",
"search_query_tables",
"retrieve_query_table",
"execute_query_template",
"retrieve_query_template"
],
"type": "string",
"description": "The intent of the tool call."
},
"params": {
"type": "object",
"properties": {
"sql": {
"type": "string",
"description": "Used with execute_query_run. The SQL query to execute (Trino 414)."
},
"grains": {
"type": "array",
"items": {
"enum": [
"day",
"week",
"month"
],
"type": "string"
},
"description": "Used with execute_query_template. Time grain: 'day', 'week', or 'month'. Default is 'month'."
},
"metric": {
"enum": [
"gross_volume",
"subscriber_churn_rate",
"gross_mrr_churn_rate",
"churned_subscribers",
"net_mrr_churn_rate",
"churned_revenue",
"new_subscribers",
"active_subscribers",
"active_subscriber_growth"
],
"type": "string",
"description": "Used with execute_query_template. The canonical metric name."
},
"dimensions": {
"type": "array",
"items": {
"enum": [
"product",
"price"
],
"type": "string"
},
"description": "Used with execute_query_template. Dimensions to group by: 'product', 'price'."
},
"table_name": {
"type": "string",
"pattern": "^[a-zA-Z0-9_]+$",
"description": "Used with retrieve_query_table. The table name."
},
"query_run_id": {
"type": "string",
"pattern": "^(qryrun|qrun)_[a-zA-Z0-9_]+$",
"description": "Used with retrieve_query_run or retrieve_query_template. The QueryRun ID to retrieve."
},
"search_string": {
"type": "string",
"description": "Used with search_query_tables. Keyword to search table names and descriptions."
},
"metric_filters": {
"type": "array",
"items": {
"enum": [
"top5"
],
"type": "string"
},
"description": "Used with execute_query_template. Filters to apply: 'top5' or 'all'. Default is 'all'."
},
"result_options": {
"type": "object",
"properties": {
"compression": {
"enum": [
"none",
"zip"
],
"type": "string",
"description": "Compression applied to the generated results file. Defaults to none."
}
},
"description": "Used with execute_query_run. Optional settings for the QueryRun results."
}
},
"description": "The parameters for the tool call. Required parameters depend on the intent."
}
}
}Get detailed parameter information for a specific Stripe API operation. Provide the stripe_api_operation_id from stripe_api_search results to see all path, query, and body paramet…
| Argument | Type | Description |
|---|---|---|
| stripe_api_operation_id* | string | The operation ID to get details for (e.g. 'PostCustomers', 'GetPaymentIntents') |
{
"type": "object",
"required": [
"stripe_api_operation_id"
],
"properties": {
"stripe_api_operation_id": {
"type": "string",
"description": "The operation ID to get details for (e.g. 'PostCustomers', 'GetPaymentIntents')"
}
}
}Read data from any Stripe API GET operation: 1. Use stripe_api_search to find the operation ID. 2. Use stripe_api_details to see its parameters, unless the search result already l…
| Argument | Type | Description |
|---|---|---|
| parameters | object | All path, query, and request-body values for the API call. Include path parameters here, named as in the path's curly braces (e.g. 'id' for /v1/customers/{id}). Array fields (e.g. line_items) must be passed as a JSON array value, not as a plain string. |
| stripe_api_operation_id* | string | The operation ID to execute |
{
"type": "object",
"required": [
"stripe_api_operation_id"
],
"properties": {
"parameters": {
"type": "object",
"description": "All path, query, and request-body values for the API call. Include path parameters here, named as in the path's curly braces (e.g. 'id' for /v1/customers/{id}). Array fields (e.g. line_items) must be passed as a JSON array value, not as a plain string."
},
"stripe_api_operation_id": {
"type": "string",
"examples": [
"PostCustomers",
"GetPaymentIntents"
],
"description": "The operation ID to execute"
}
}
}Search for Stripe API operations by providing an intent and a resource to operate on. For the resource, use a specific, descriptive phrase (e.g. "issuing card transactions", "pay…
| Argument | Type | Description |
|---|---|---|
| limit | integer | Maximum number of results to return |
| intent* | string | The intent of the operation |
| resource* | string | Target resource the operation is looking to manipulate |
{
"type": "object",
"required": [
"intent",
"resource"
],
"properties": {
"limit": {
"type": "integer",
"default": 5,
"maximum": 20,
"minimum": 1,
"description": "Maximum number of results to return"
},
"intent": {
"type": "string",
"examples": [
"create",
"list",
"refund"
],
"description": "The intent of the operation"
},
"resource": {
"type": "string",
"examples": [
"customer",
"payout methods",
"issuing card transactions"
],
"description": "Target resource the operation is looking to manipulate"
}
}
}Write data via any Stripe API POST/PATCH/PUT/DELETE operation: 1. Use stripe_api_search to find the operation ID. 2. Use stripe_api_details to see its parameters, unless the searc…
| Argument | Type | Description |
|---|---|---|
| parameters | object | All path, query, and request-body values for the API call. Include path parameters here, named as in the path's curly braces (e.g. 'id' for /v1/customers/{id}). Array fields (e.g. line_items) must be passed as a JSON array value, not as a plain string. |
| human_confirmation | object | This tool might require human confirmation. To run it, first invoke it with the desired parameters, ignoring the `approval_token` parameter. If it requires human confirmation, the response will include an approval request ID and a URL to an approval page for the human to approve the tool call. You, as the LLM agent, should: 1. Present this URL to the human as a clickable markdown link. Tell them that they have to approve this tool call at that URL, and that they should tell you when they have approved the operation. 2. The human will approve that call. 3. After the human tells you they have approved the operation, you must call the tool again with the `approval_token` parameter and the exact same parameters. The operation will then go through. |
| stripe_api_operation_id* | string | The operation ID to execute |
{
"type": "object",
"required": [
"stripe_api_operation_id"
],
"properties": {
"parameters": {
"type": "object",
"description": "All path, query, and request-body values for the API call. Include path parameters here, named as in the path's curly braces (e.g. 'id' for /v1/customers/{id}). Array fields (e.g. line_items) must be passed as a JSON array value, not as a plain string."
},
"human_confirmation": {
"type": "object",
"properties": {
"approval_token": {
"type": "string",
"description": "The ID of the approval token for the request. This is required on only the post-human-confirmation invocation. An example ID is `approval_123`."
}
},
"description": "This tool might require human confirmation. To run it, first invoke it with the desired parameters, ignoring the `approval_token` parameter.\nIf it requires human confirmation, the response will include an approval request ID and a URL to an approval page for the human to approve the tool call.\nYou, as the LLM agent, should:\n\n1. Present this URL to the human as a clickable markdown link. Tell them that they have to approve this tool call at that URL, and that they should tell you when they have approved the operation.\n2. The human will approve that call.\n3. After the human tells you they have approved the operation, you must call the tool again with the `approval_token` parameter and the exact same parameters. The operation will then go through.\n"
},
"stripe_api_operation_id": {
"type": "string",
"examples": [
"PostCustomers",
"GetPaymentIntents"
],
"description": "The operation ID to execute"
}
}
}Stripe integration planner. Use this tool to help users accept payments, sell products online, set up billing, set up a marketplace or platform, or build any Stripe integration. C…
| Argument | Type | Description |
|---|---|---|
| accept | boolean | Set to true when returning the completed decision trees with your chosen options. Include selected_leaf_nodes with the IDs of all terminal leaves reached. |
| message | string | For new guides: describe the use case or business requirements. |
| guide_id | string | ONLY pass a guide_id that was returned by a previous call to this tool in this conversation. Never fabricate, guess, or reuse guide_ids from other sessions. If you do not have a guide_id from a prior response, omit this field entirely. Invalid guide_ids will be rejected. |
| selected_leaf_nodes | array | The IDs of all terminal leaves reached while traversing the guide's decision tree. |
{
"type": "object",
"required": [],
"properties": {
"accept": {
"type": "boolean",
"description": "Set to true when returning the completed decision trees with your chosen options. Include selected_leaf_nodes with the IDs of all terminal leaves reached."
},
"message": {
"type": "string",
"description": "For new guides: describe the use case or business requirements."
},
"guide_id": {
"type": "string",
"description": "ONLY pass a guide_id that was returned by a previous call to this tool in this conversation. Never fabricate, guess, or reuse guide_ids from other sessions. If you do not have a guide_id from a prior response, omit this field entirely. Invalid guide_ids will be rejected."
},
"selected_leaf_nodes": {
"type": "array",
"items": {
"type": "string"
},
"description": "The IDs of all terminal leaves reached while traversing the guide's decision tree."
}
}
}