Artifyde MCP server
{
"mcpServers": {
"artifyde": {
"command": "npx",
"args": [
"-y",
"artifyde-mcp@latest"
],
"env": {
"ARTIFYDE_TOKEN": "<artifyde_token>",
"ARTIFYDE_API_KEY": "<artifyde_api_key>",
"ARTIFYDE_URL": "https://..."
}
}
}
}{
"mcpServers": {
"artifyde": {
"command": "npx",
"args": [
"-y",
"artifyde-mcp@latest"
],
"env": {
"ARTIFYDE_TOKEN": "<artifyde_token>",
"ARTIFYDE_API_KEY": "<artifyde_api_key>",
"ARTIFYDE_URL": "https://..."
}
}
}
}{
"mcpServers": {
"artifyde": {
"command": "npx",
"args": [
"-y",
"artifyde-mcp@latest"
],
"env": {
"ARTIFYDE_TOKEN": "<artifyde_token>",
"ARTIFYDE_API_KEY": "<artifyde_api_key>",
"ARTIFYDE_URL": "https://..."
}
}
}
}{
"servers": {
"artifyde": {
"command": "npx",
"args": [
"-y",
"artifyde-mcp@latest"
],
"env": {
"ARTIFYDE_TOKEN": "${input:artifyde_token}",
"ARTIFYDE_API_KEY": "${input:artifyde_api_key}",
"ARTIFYDE_URL": "${input:artifyde_url}"
}
}
},
"inputs": [
{
"id": "artifyde_token",
"type": "promptString",
"description": "Artifyde token",
"password": true
},
{
"id": "artifyde_api_key",
"type": "promptString",
"description": "Artifyde api key",
"password": true
},
{
"id": "artifyde_url",
"type": "promptString",
"description": "Artifyde url",
"password": true
}
]
}{
"mcpServers": {
"artifyde": {
"command": "npx",
"args": [
"-y",
"artifyde-mcp@latest"
],
"env": {
"ARTIFYDE_TOKEN": "<artifyde_token>",
"ARTIFYDE_API_KEY": "<artifyde_api_key>",
"ARTIFYDE_URL": "https://..."
}
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y artifyde-mcpversion 0.1.2
What it does
An MCP server that publishes HTML artifacts (dashboards, prototypes, reports) generated by AI agents to Artifyde, giving them permanent stable URLs, version history, and sharing capabilities. It is for developers using Claude, Cursor, or other MCP-capable clients who want their agent's output to persist beyond a single session.
- Publish an HTML dashboard or prototype your agent generates and get a shareable stable URL that persists across runs.
- Retrieve and re-publish a previous artifact to create a new version with full version history and change tracking.
- Manage access to artifacts by setting visibility to public or private, inviting specific emails, and organizing pages into gallery shelves.
Tools this server exposes
| Tool | Does |
|---|---|
| push_artifact | Publish HTML to a stable view URL; re-push with a page_id to create a new version. |
| pull_artifact | Download a version's HTML in its exact original form. |
| get_page | Retrieve page metadata and version history. |
| list_pages | List your pages with version and comment counts, optionally filtered by archived status or search query. |
| rename_page | Change a page's display title. |
| archive_page | Hide a page and make it read-only. |
| unarchive_page | Restore a hidden page to active status. |
| get_share | View a page's visibility setting and list of invited email addresses. |
| set_visibility | Set a page to public or private. |
| share_page | Invite an email address to access a private page. |
| unshare_page | Revoke an email address's access to a private page. |
| list_comments | Read all comment threads on a page. |
| create_comment | Post a new comment or reply on a version. |
| list_shelves | View gallery groupings. |
| create_shelf | Create a new shelf for organizing pages. |
| add_page_to_shelf | Add a page to a shelf. |
| remove_page_from_shelf | Remove a page from a shelf. |
| whoami | Return the identity (user or service account) the server is authenticated as. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.