How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Smithery

Smithery connect API

The connect API from Smithery — 12 operation(s) for connect.

Documentation Provider Profile APIs.io OpenAPI GitHub

Smithery connect API is one of 9 APIs that Smithery publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 3 JSON Schema definitions.

Tagged areas include Connect. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a JSON-LD context, rate-limit docs, and 3 JSON Schemas.

This API exposes 21 operations across 12 paths, and defines 27 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.smithery.ai.

21 operations 12 paths 27 schemas 5 DELETE10 GET5 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.smithery.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Smithery connect API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Smithery API key as Bearer token

Paths & Operations 21

Across 12 paths, the API surfaces 21 operations — 5 DELETE, 10 GET, 5 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

connect 21
GET
/connect/{namespace}
List connections
getSmithery.run:namespace 5 params → 200400
POST
/connect/{namespace}
Create connection
postSmithery.run:namespace 1 param body → 201400404
GET
/connect/{namespace}/{connectionId}/.triggers
List triggers
getSmithery.run:namespace:connectionId.triggers 2 params → 200404
GET
/connect/{namespace}/{connectionId}/.triggers/{triggerName}
Get trigger
getSmithery.run:namespace:connectionId.triggers:triggerName 3 params → 200404
POST
/connect/{namespace}/{connectionId}/.triggers/{triggerName}
Subscribe to trigger
postSmithery.run:namespace:connectionId.triggers:triggerName 3 params body → 200400404
DELETE
/connect/{namespace}/{connectionId}/.triggers/{triggerName}
Unsubscribe from trigger
deleteSmithery.run:namespace:connectionId.triggers:triggerName 3 params body → 200404
GET
/connect/{namespace}/{connectionId}
Get connection
getSmithery.run:namespace:connectionId 2 params → 200400404
PUT
/connect/{namespace}/{connectionId}
Create or update connection
putSmithery.run:namespace:connectionId 2 params body → 200201400404409
DELETE
/connect/{namespace}/{connectionId}
Delete connection
deleteSmithery.run:namespace:connectionId 2 params → 200400404
GET
/connect/{namespace}/.tools
List tools across a namespace
getSmithery.run:namespace.tools 1 param → 200
GET
/connect/{namespace}/{connectionId}/.tools
List tools
getSmithery.run:namespace:connectionId.tools 2 params → 200404
GET
/connect/{namespace}/{connectionId}/.tools/{toolPath}
Get tool
getSmithery.run:namespace:connectionId.tools:toolPath 3 params → 200404
POST
/connect/{namespace}/{connectionId}/.tools/{toolPath}
Call tool
postSmithery.run:namespace:connectionId.tools:toolPath 3 params body → 200400404422
GET
/connect/{namespace}/.subscriptions
List namespace subscriptions
getSmithery.run:namespace.subscriptions 1 param → 200
POST
/connect/{namespace}/.subscriptions
Create namespace subscription
postSmithery.run:namespace.subscriptions 1 param → 200400
DELETE
/connect/{namespace}/.subscriptions/{subscriptionId}
Delete namespace subscription
deleteSmithery.run:namespace.subscriptions:subscriptionId 2 params → 200404
GET
/connect/{namespace}/{connectionId}/.triggers/{triggerName}/{triggerId}
Get trigger instance
getSmithery.run:namespace:connectionId.triggers:triggerName:triggerId 4 params → 200404
DELETE
/connect/{namespace}/{connectionId}/.triggers/{triggerName}/{triggerId}
Delete trigger instance
deleteSmithery.run:namespace:connectionId.triggers:triggerName:triggerId 4 params → 200404
GET
/connect/{namespace}/{connectionId}/.subscriptions
List connection subscriptions
getSmithery.run:namespace:connectionId.subscriptions 2 params → 200404
POST
/connect/{namespace}/{connectionId}/.subscriptions
Create connection subscription
postSmithery.run:namespace:connectionId.subscriptions 2 params → 200400404
DELETE
/connect/{namespace}/{connectionId}/.subscriptions/{subscriptionId}
Delete connection subscription
deleteSmithery.run:namespace:connectionId.subscriptions:subscriptionId 3 params → 200404

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are Connection (10 properties), Tool (9 properties), CreateConnectionRequest (6 properties), ServerInfo (6 properties). Each schema is shown below with its type and property counts.

ConnectionsListResponse
object
2 properties 2 required
LooseObject
object
DeleteTriggerRequest
object
2 properties 2 required
Error
object
2 properties 2 required
CreateSubscriptionResponse
object
5 properties 5 required
HttpInputField
object
3 properties 1 required
CredentialProfileHttp
object
2 properties
Subscription
object
4 properties 4 required
TriggerDelivery
object
2 properties 2 required
TriggerInstance
object
5 properties 5 required
TriggerSubscription
object
2 properties 2 required
UpsertConnectionRequest
object
6 properties
ToolResponse
Success
object
1 property 1 required
CreateConnectionRequest
object
6 properties
Connection
object
10 properties 4 required
ToolList
object
1 property 1 required
MockConfig
object
2 properties 1 required
SubscriptionList
array
ConnectionStatus
ServerInfo
object
6 properties 2 required
TriggerDefinition
object
5 properties 2 required
Tool
object
9 properties 2 required
TriggerDefinitionList
array
ValidationError
object
2 properties 2 required
UnsubscribeDelivery
object
1 property 1 required
CreateTriggerRequest
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

smithery-connect-api-openapi.yml Raw ↑

Other APIs Smithery publishes across the network.

Smithery connect.mcp API
AE Profile APIs.io
Smithery domains API
AE Profile APIs.io
Smithery Health API
AE Profile APIs.io
Smithery namespaces API
AE Profile APIs.io
Smithery organizations API
AE Profile APIs.io
Smithery servers API
AE Profile APIs.io
Smithery skills API
AE Profile APIs.io
Smithery tokens API
AE Profile APIs.io
#Connect
← Back to S APIs
API Details
ID
smithery:smithery-connect-api
Base URL
https://api.smithery.ai
Docs
https://smithery.ai/docs
Provider
Smithery
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=smithery-connect-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/smithery-connect-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Smithery connect API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.