Other · Remote MCP server
FigurePages
Publish self-contained HTML/SVG pages to private, shareable URLs and control who can view them.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.figurepages/figurepages- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-12
- Updated
- 2026-08-12
- Publisher
- com.figurepages
- Namespace
- Namespace verified by the MCP Registry via the domain figurepages.com · how
- Website
- figurepages.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://figurepages.com/account/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect FigurePages
FigurePages is a remote MCP server: there is nothing to install. Its endpoint is https://figurepages.com/account/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| figma-vaultFigma designs pulled once into a local vault; AI agents read them offline with no rate limits. | Local · stdio |
| figmanageLet agents manage your Figma workspace. 102 tools for seats, teams, offboarding, and cleanup. | Local · stdio |
| FigmeMCP server that reads local Figma.fig files, fully offline. | Local · stdio |
| Figsnap MCPThe Figma file you have open, as MCP tools. Extract, edit, and keep a saved set. | Local · stdio |
| FileDir tree, file stats, duplicates, LOC for AI agents. | Local · stdio |
| File Path CheckCheck whether a path looks safe. No disk access. | Remote · HTTPLive check: ✓ handshake |
| File StorageUpload files and get public CDN links in chat. | Remote · HTTPLive check: sign-in required |
| Filekiwi MCP ServerUpload files to file.kiwi and get shareable links instantly. | Local · stdio |