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 servers API

The servers API from Smithery — 11 operation(s) for servers.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

This API exposes 4 JSON Schema definitions.

Tagged areas include Servers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 4 JSON Schemas.

This API exposes 18 operations across 11 paths, and defines 30 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.

18 operations 11 paths 30 schemas 3 DELETE9 GET1 PATCH1 POST4 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 servers API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth).

  • bearerAuth — Smithery API key as Bearer token

Paths & Operations 18

Across 11 paths, the API surfaces 18 operations — 3 DELETE, 9 GET, 1 PATCH, 1 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

servers 18
GET
/servers/{qualifiedName}
Get a server
getServers:namespace 1 param → 200404
PUT
/servers/{qualifiedName}
Create a server
putServers:namespace 1 param body → 201400401403404
PATCH
/servers/{qualifiedName}
Update a server
patchServers:namespace 1 param body → 200400403404
DELETE
/servers/{qualifiedName}
Delete a server
deleteServers:namespace 1 param → 200404
GET
/servers/{qualifiedName}/download
Download server bundle
getServers:namespaceDownload 1 param → 200404
PUT
/servers/{qualifiedName}/releases
Publish a server
putServers:namespaceReleases 1 param body → 202400
GET
/servers/{qualifiedName}/releases
List releases
getServers:namespaceReleases 3 params → 200404
GET
/servers/{qualifiedName}/releases/{id}
Get a release
getServers:namespaceReleases:id 2 params → 200404
GET
/servers/{qualifiedName}/releases/{id}/stream
Stream release logs
getServers:namespaceReleases:idStream 2 params → 200404
POST
/servers/{qualifiedName}/releases/{id}/resume
Resume a release
postServers:namespaceReleases:idResume 2 params → 202400404
GET
/servers/{qualifiedName}/logs
List runtime logs
getServers:namespaceLogs 5 params → 200403404500
GET
/servers/{qualifiedName}/secrets
List secrets
getServers:namespaceSecrets 1 param → 200404
PUT
/servers/{qualifiedName}/secrets
Set a secret
putServers:namespaceSecrets 1 param body → 200404
DELETE
/servers/{qualifiedName}/secrets/{secretName}
Delete a secret
deleteServers:namespaceSecrets:secretName 2 params → 200404
PUT
/servers/{qualifiedName}/icon
Upload server icon
putServers:namespaceIcon 1 param → 200400403404
DELETE
/servers/{qualifiedName}/icon
Delete server icon
deleteServers:namespaceIcon 1 param → 200403404
GET
/servers/{qualifiedName}/icon
Get server icon
getServers:namespaceIcon 1 param → 200404
GET
/servers
List all servers
getServers 15 params → 200400401422

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are ServerSummary (16 properties), Server (11 properties), DeploymentInfo (11 properties), Invocation (7 properties). Each schema is shown below with its type and property counts.

ConfigSchema
object
ServerSecurity
object
1 property 1 required
RuntimeLogsError
object
1 property 1 required
RegistryError
object
1 property 1 required
ServerTool
object
4 properties 3 required
ToolInputSchema
object
2 properties 1 required
InvocationDuration
object
2 properties 2 required
InputSchemaProperties
object
ServersListError
object
1 property 1 required
InvocationResponse
object
2 properties 2 required
StdioConnection
object
4 properties 4 required
ServersListResponse
object
2 properties 2 required
ResumeResponse
object
2 properties 2 required
InvocationRequest
object
2 properties 2 required
DeploymentInfo
object
11 properties 5 required
HttpConnection
object
3 properties 3 required
ExceptionEntry
object
3 properties 3 required
DeploymentLogEntry
object
5 properties 4 required
RuntimeLogEntry
object
3 properties 3 required
RuntimeLogsResponse
object
2 properties 2 required
DeploymentError
object
1 property 1 required
DeployResponse
object
4 properties 3 required
OutputSchemaProperties
object
ToolOutputSchema
object
3 properties 1 required
DeploymentLogEntryError
object
1 property
ServerResource
object
4 properties 2 required
Invocation
object
7 properties 7 required
ServerPrompt
object
3 properties 1 required
Server
object
11 properties 11 required
ServerSummary
object
16 properties 16 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

smithery-ai-servers-api-openapi.yml Raw ↑

Other APIs Smithery publishes across the network.

Smithery connect API
AE Profile APIs.io
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 skills API
AE Profile APIs.io
Smithery tokens API
AE Profile APIs.io
#Servers
← Back to S APIs
API Details
ID
smithery-ai:smithery-ai-servers-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-ai-servers-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/smithery-ai-servers-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 servers 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.