Artifact Share MCP API

The Mcp API from Artifact Share — 1 operation(s) for mcp.

Operations 1

POST /mcp MCP endpoint (JSON-RPC over Streamable HTTP) #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/artifactshare-com:artifactshare-com-mcp-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

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

OpenAPI Specification

artifactshare-com-mcp-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Artifact Share MCP API
  version: 0.1.0
  description: Artifact Share is reached programmatically through its remote MCP endpoint at /mcp (JSON-RPC over Streamable HTTP) and authenticated CLI REST endpoints. An MCP client (Claude, ChatGPT, Cursor) authorizes with OAuth 2.1 and then calls tools to share, update, read, comment on, and organize artifacts. See /capabilities.md for the full tool list and /.well-known/agent.json for discovery.
servers:
- url: https://artifactshare.com
tags:
- name: MCP
paths:
  /mcp:
    post:
      summary: MCP endpoint (JSON-RPC over Streamable HTTP)
      description: Publisher device credentials are limited to their scoped artifact REST endpoints and cannot access MCP. Remote MCP server. Accepts JSON-RPC 2.0 (initialize, tools/list, tools/call) with an OAuth 2.1 bearer token. See /capabilities.md for the full tool list.
      security:
      - oauth2:
        - artifactshare:access
      responses:
        '200':
          description: JSON-RPC response.
        '401':
          description: Missing or invalid bearer token; the WWW-Authenticate header points at the protected-resource metadata.
      tags:
      - MCP
      operationId: postMcp
      x-operation-id-source: derived
components:
  securitySchemes:
    cliBearer:
      type: http
      scheme: bearer
      description: CLI access credential; not an MCP OAuth token.
    browserSession:
      type: apiKey
      in: cookie
      name: better-auth.session_token
      description: Authenticated browser session (secure cookie name may carry the __Secure- prefix).
    oauth2:
      type: oauth2
      description: OAuth 2.1 authorization-code flow with PKCE, served under /api/auth. MCP clients obtain the bearer token for /mcp this way; the same endpoints are advertised at /.well-known/oauth-authorization-server.
      flows:
        authorizationCode:
          authorizationUrl: https://artifactshare.com/api/auth/oauth2/authorize
          tokenUrl: https://artifactshare.com/api/auth/oauth2/token
          scopes:
            openid: Authenticate the user
            profile: Read basic profile (name, locale)
            email: Read the verified email address
            offline_access: Issue a refresh token for offline use
            artifactshare:access: View, share, update, and permanently delete Artifact Share files; manage projects and comments