Vinkius
Mirror.xyz

Mirror.xyz MCP for AI. Access decentralized Web3 articles via prompt.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Mirror.xyz (Web3 Publishing Platform) MCP on Cursor AI Code EditorMirror.xyz (Web3 Publishing Platform) MCP on Claude Desktop AppMirror.xyz (Web3 Publishing Platform) MCP on OpenAI Agents SDKMirror.xyz (Web3 Publishing Platform) MCP on Visual Studio CodeMirror.xyz (Web3 Publishing Platform) MCP on GitHub Copilot AI AgentMirror.xyz (Web3 Publishing Platform) MCP on Google Gemini AIMirror.xyz (Web3 Publishing Platform) MCP on Lovable AI DevelopmentMirror.xyz (Web3 Publishing Platform) MCP on Mistral AI AgentsMirror.xyz (Web3 Publishing Platform) MCP on Amazon AWS Bedrock

How this MCP server connects to your AI agent

Mirror.xyz connects your agent directly to decentralized content hosted on Arweave and ENS domains. Use this server to fetch lists of publications for a given ENS name or retrieve the full text and metadata for any specific entry using its unique Arweave digest.

What AI agents can do with Mirror.xyz (Web3 Publishing Platform) Automation

Get entries

Fetches a list of all published entries for a specified Mirror publication using its ENS name.

Get entry

Retrieves the full content, metadata, and author details for one specific Mirror entry using its Arweave digest.

List all publication entries

You give it an ENS name, and it returns a list of the latest published links for that specific Mirror profile.

Retrieve full article content

You provide a unique Arweave digest, and it fetches the complete text, title, and author information for that single decentralized post.

Analyze Web3 data streams

Your AI client uses the retrieved data to summarize project updates or analyze governance proposals published on Mirror.xyz.

Included with Plan

Waiting for input…

AI Agent

What AI agents can do with Mirror.xyz Web3 Publishing Platform: 2 Tools for Content Retrieval

Use these two tools to fetch publication entries by name or retrieve the complete text of a single decentralized article using its unique digest.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using Mirror.xyz (Web3 Publishing Platform) on Vinkius

Get Entries

Fetches a list of all published entries for a specified Mirror publication using its ENS name.

Get Entry

Retrieves the full content, metadata, and author details for one specific Mirror...

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Claude AI

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

3

Start a conversation

Open a new chat. The Mirror.xyz integration is available immediately — no restart needed.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with Mirror.xyz (Web3 Publishing Platform), then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 5,100+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week
Mirror.xyz MCP server cover

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Mirror.xyz. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This connection provides 2 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

Finding decentralized articles shouldn't require three different websites and six tabs open., Solved with Vinkius AI Gateway

Right now, tracking content from Web3 is painful. You find an ENS name, you have to go to the publishing site, check their archive page for a list of links, then copy each digest one by one into Arweave's public viewer just to read it. This process takes minutes and guarantees human error.

With this MCP server, your agent handles the whole chain. You give it the ENS name, it runs `get_entries`, gives you the list, and if you point to a specific digest, `get_entry` pulls the full article text into plain language right where you're working.

Mirror.xyz MCP Server: Get entries or fetch content by digest.

The old way meant navigating between ENS domains, arweave viewers, and block explorers just to assemble a single article's context—a tedious copy/paste nightmare every time you needed historical data. Now, your agent runs the specific tool. If you want the list, call `get_entries`. If you have the ID, use `get_entry`. You get the data instantly, structured and ready for analysis.

What your AI can actually do with this

Mirror.xyz connects your agent straight into decentralized content on Arweave and ENS domains. You'll use this server when you need your AI client to handle web3 data, bypassing traditional search engines or centralized APIs. It provides two core functions for deep content retrieval: one tool lists publications using an ENS name, and the other pulls the complete article details from a specific Arweave digest.

When you run get_entries, you hand it an ENS name—say, yourproject.eth—and it returns a clean list of every publication that's been posted under that Mirror profile. This isn't just metadata; it's the working index for all available content associated with that specific decentralized identity. You get a bulletproof log of links and timestamps showing you exactly what was published, letting your agent track project timelines or editorial history for any given Web3 entity.

If you know which article you want, get_entry is your play. It takes the unique Arweave digest—that long string of characters pointing to the data block—and pulls back everything attached to that single post. You don't just get the text; you get the full content body, the title, and all the metadata about the entry, including who authored it and when.

This is crucial because knowing the author isn't enough; you need the context of the submission itself.

Your agent can use these mechanisms to analyze web3 data streams by pulling multiple pieces of information. For example, if a project publishes a governance proposal on Mirror, your client uses get_entry with the digest to pull the full text of that proposal, and then it might run get_entries first to see when the proposal was published relative to other announcements.

You can build complex research flows—the agent pulls a list via ENS name, picks the most relevant link from that list, and then uses the Arweave digest on that link to get all the details needed for a summary or analysis.

Think about it: you're not manually checking block explorers anymore. Your client acts like a dedicated web3 librarian, querying the source of truth directly. If you need to summarize project updates across several months of decentralized journalism, your agent doesn't guess; it gets the raw data points for every entry needed.

When analyzing governance proposals or market commentary published on Mirror.xyz, you can feed the complete text from get_entry into your AI client. You don't have to sift through boilerplate language. The tool gives you the actual words and the associated author details, so you're working with verifiable primary source material.

This capability means you can build logic that tracks shifts in sentiment or changes in technical focus across a series of posts—it’s all about the data flow.

It’s simple: give your agent an ENS name to see what’s out there, or give it a digest to read exactly what was said. You'll use these tools to build workflows that summarize project activity or analyze complex discussions by pulling structured lists and then deep-diving into the full text of each piece of content retrieved from Arweave.

Built · Hosted · Managed by Vinkius Mirror.xyz MCP Server - Decentralized Content Retrieval
Server ID 019e5d36-3ba9-720b-baf6-b71cf4db9a02
Vinkius Inspector
Compliance Grade A+
Score 100/100
Vinkius Inspector Badge — Score 100/100

Questions you might have

How do I use the get_entries tool with Mirror.xyz? +

You prompt your agent by asking to list entries for a specific ENS name (e.g., 'List all posts for my-blog.eth'). The get_entries tool handles fetching the list of publication links.

What is an Arweave digest and why do I need get_entry? +

The Arweave digest is a unique, permanent ID for a piece of data. You use get_entry when you have this specific ID because it guarantees the agent retrieves that exact, full article's content.

Can I use get_entries to find all posts by an author? +

You can list entries for a specific ENS name. If the author published under their own dedicated publication name, you can query that; otherwise, you need the author's specific profile ENS.

Does this server work with other Web3 platforms besides Mirror? +

No. This server is specifically built to interface with the content standards and data structures used by Mirror.xyz on Arweave.

What credentials do I need when calling get_entries? +

You might need to provide a Mirror Developer API key. If you're only targeting publicly visible publications, the server often handles the request without explicit authentication. Using your own key guarantees access to all available data.

If I call get_entry with an incorrect Arweave digest, what happens? +

The server returns a specific 'Entry Not Found' error. This means the provided digest doesn't map to any valid content on Mirror. Double-check that the digest is correct and hasn't been corrupted.

Does calling get_entries repeatedly trigger rate limits? +

Yes, rapid calls to get_entries can hit usage limits. We recommend implementing an exponential backoff strategy in your AI client. This prevents throttling and keeps your data retrieval stable.

When I use get_entries, does the publication ENS name require a specific format? +

Yes, the ENS name must be fully qualified for accurate results. When you pass mirror-xyz.eth, ensure your client passes it exactly as registered on Mirror to fetch all associated entries.

Can I fetch posts from any Mirror publication if I only have the ENS domain? +

Yes! Use the get_entries tool with the ENS domain (e.g., 'mirror-xyz.eth'). The agent will return a list of published entries associated with that specific publication.

How do I retrieve the full text of a specific Mirror article? +

You can use the get_entry tool by providing the unique Arweave digest (transaction hash) of the article. This will fetch the full content, title, and author details.

Does this integration allow me to publish new content to Mirror.xyz? +

No. The current set of tools is focused on querying and reading data (fetching entries and entry details). Publishing operations are not supported in this version.

Built & Managed by Vinkius 30s setup 2 tools

We've already built the connector for Mirror.xyz. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 2 tools are live and waiting. You're up and running in seconds.

Vinkius runs on Claude Claude
Vinkius runs on ChatGPT ChatGPT
Vinkius runs on Cursor Cursor
Vinkius runs on Gemini Gemini
Vinkius runs on Windsurf Windsurf
Vinkius runs on VS Code VS Code
Vinkius runs on JetBrains JetBrains
Vinkius runs on Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.