MCP server · Archive Technologies

archive

Archive operates an official hosted remote MCP server at https://app.archive.com/api/v2/mcp, discoverable via RFC 9728 protected-resource metadata (well-known/archive-technologies-oauth-protected-resource.json) and authorized by the OAuth authorization server at https://app.archive.com (RFC 8414 metadata in well-known/archive-technologies-oauth-authorization-server.json). The server is OAuth-protected: authorization_code + refresh_token grants, PKCE S256, dynamic client registration (/oauth/register) and a single "mcp" scope; no client id/secret is issued to connector authors. Archive publishes the complete tool catalog at https://api-docs.archive.com/mcp — 53 tools, 29 read and 24 write — and states the page is kept in sync with the live server. The tool list below is transcribed verbatim from that page. A live tools/list call is NOT anonymous: it returns HTTP 401 with a WWW-Authenticate Bearer challenge pointing at the protected-resource metadata, so per-tool inputSchema requires an authenticated introspection and is not asserted here. Each tool maps to a GraphQL query or mutation on the same API and spends the same per-workspace credit budget (see mcp/archive-technologies-tool-crosswalk.yml and rate-limits/archive-technologies-rate-limits.yml).

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

Provider: Archive Technologies Type: Hosted endpoint Transport: http Host: app.archive.com

Endpoint

https://app.archive.com/api/v2/mcp

Hosted endpoint · transport http

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

# mcp client config (e.g. .mcp.json / mcp settings) { "mcpServers": { "archive-technologies": { "url": "https://app.archive.com/api/v2/mcp" } } }

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

# Add to claude_desktop_config.json { "mcpServers": { "archive-technologies": { "command": "npx", "args": ["-y", "mcp-remote", "https://app.archive.com/api/v2/mcp"] } } }

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

curl -i -X POST https://app.archive.com/api/v2/mcp \ -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tools

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.