Claude

How to give Claude access to ReadMe

Set up in seconds, once. From then on, Claude gets things done for you: it checks ReadMe, does the legwork, and brings the answer back into the conversation.

Ask AI about this guide

ReadMe Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_65dP2ZEWi1ggQrtmq1IKVpZ6MOAhFxi6q98C5XwC/mcp

Connecting ReadMe to Claude

About a minute, right in your Claude settings

  1. 1In Claude, open Customize and choose Connectors (claude.ai or the desktop app).
  2. 2Click +, choose Add custom connector, and paste your ReadMe link as the remote MCP server URL.
  3. 3Click Add and start a new chat. Ask for something real: ReadMe is now part of your Claude.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "readme-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_65dP2ZEWi1ggQrtmq1IKVpZ6MOAhFxi6q98C5XwC/mcp"
    }
  }
}

Claude + ReadMe

One chat. Your ReadMe, live inside Claude.

Real prompts, answered with live data. This is the kind of conversation you will have in Claude once the link is in.

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

These prompts ship with the ReadMe Connector. Once yours is connected, they work in your chats.

The full capability set, the prompts and the observed latency live on the ReadMe Connector page.

Mission Control

See everything your Claude agents do in ReadMe.

When Claude runs a tool in ReadMe, it happens on Claude's side: you see the answer in the chat, but not the request itself, what data it carried, or whether a rule was broken.

Now every move lands on your screen.

Every execution is recorded, enforced, and shown to you: what ran, what it returned, what was blocked, and why.

AI Briefing
Upgrade to unlock

Know exactly what needs your attention before you even look at the charts. One briefing. The full picture. The next move.

Requests
0
Total in this period
Avg Latency
0
API 88ms · Overhead 54ms
Vinkius Reliability
0
Agent 280 · Upstream 47 · Vinkius 15
Tokens
0
AI tokens processed
DLP Protected
0
Sensitive data redacted
Cost Saved
0
FinOps truncations applied

AI Agents Activities

last 30 days
30d agotoday

Request Volume & Latency

requests latency

Every request your Claude agents make through ReadMe is logged, enforced and auditable. See how AI Governance turns agent activity into accountability, and what it means for your ReadMe workflows.

What sets us apart

It's not just the Connector that stays safe. Everything your agents do through it is.

Connecting ReadMe to your AI is step one. But an open line between your agents and ReadMe is only half the story: without protection, every action they take runs unguarded.

That's why protection doesn't stop at the door.

Every action your agents take through the Connector runs inside our infrastructure: signed activity logs, automatic key rotation, spending limits that pause instead of surprise, and a sandbox that isolates every execution.

01

Tamper Proof Activity Log

Every request your agents make in ReadMe is recorded and signed, so any change to the history becomes detectable.

02

Automatic Key Rotation

We rotate security keys every 24 hours. Your ReadMe connection stays protected without any manual work.

03

Spending Protection

We enforce the spending limit you choose and pause actions that exceed it until approval is received. Your ReadMe actions never surprise you.

04

Isolated Sandbox

Every execution through ReadMe runs isolated, with 34+ security rules covering memory, CPU, network access, file handling and execution.

05

Security Event Streaming

Security events flow to Splunk, Datadog or your own webhook, so ReadMe activity lands in the tools you already rely on.

06

Instant Resume

Idle connections resume in 3 to 5 ms while preserving their state, keeping your Claude conversations responsive.

07

Malicious File Protection

We detect compressed files designed to exhaust system resources and block them before they ever reach ReadMe.

08

Credential Validation

We test your ReadMe credentials before saving them. Invalid credentials are rejected instead of being stored.

09

Separate Usage Limits

Usage stays isolated per account, so activity in one connection never consumes another account's allowance.

One Connector, one link, and the whole operation is protected. Not just the connection: everything your agents do through it.

These guarantees are not add-ons: they are the infrastructure every ReadMe connection runs on. Read how our infrastructure protects everything your Claude agents do, end to end.

Inside Vinkius

Get ReadMe ready for your AI. It's easy.

You choose ReadMe from the Vinkius Catalog, sign in to your ReadMe account, and get one connection link. That's it.

  1. You choose ReadMe

    You find ReadMe in the Catalog and install the Connector with one click.

    ReadMe

    Active

    Enable Connector
    Activating…

  2. You sign in

    You connect your ReadMe account and choose what you want your AI to access. Your credentials stay encrypted and separate from your AI.

    Configure Credentials

    Configure credentials for {{connectorName}}

    RequiredEncrypted
    Save & Continue

    Encrypted Storage

    Your credentials are encrypted at rest and in transit.

    Never Shared

    Your credentials are never shared with third parties.

    Full Control

    Revoke or update credentials at any time.

  3. You add the link in Claude

    Vinkius gives you one connection link. In Claude, you open Customize, choose Connectors, click + and pick Add custom connector, then paste the link there.

    Token generated successfully

    MCP Connection URL

    https://edge.vinkius.com/vk_preview_65dP2ZEWi1ggQrtmq1IKVpZ6MOAhFxi6q98C5XwC/mcp

    Connection Token

    vk_live_••••••••
    Go to Dashboard

Set it up once. Use ReadMe with the AI you already use.

FAQ

Claude access questions.

  • 01

    Does this work on claude.ai and in the Claude desktop app?

    Yes. You add the same link under Customize and Connectors in both, and your chats work the same in each.

  • 02

    If I connect ReadMe to Claude, can I use the same connection in ChatGPT or Gemini later?

    Yes, and that's the point: the connection is yours, not Claude's. You paste the same link in any AI you use, and there's nothing new to set up or pay again. Connect a new AI and ReadMe is already there.

  • 03

    Do I need to hand my ReadMe password to Claude?

    Never. You sign in once at Vinkius, and we keep your logins encrypted and away from your AI. Claude only ever sees the link, and you can remove it whenever you want.

  • 04

    What can I actually ask Claude to do with ReadMe?

    Whatever the Connector covers: check data, run actions and bring answers back into the chat. The Connector page lists every capability your AI gains, with real examples you can copy.

  • 05

    Claude doesn't show the Connector. What do I check?

    Make sure the link was pasted exactly as copied and that the Connector is active in your Vinkius account, then reopen the connectors list in Claude. A deactivated Connector stops appearing in new chats.

  • 06

    Can I remove the access later?

    Anytime. Remove the connector under Customize and Connectors in Claude and it's out of your chats. Your Vinkius account keeps the connection and its history either way, ready for the next AI.

  • More questions about ReadMe? The Connector page answers them. See everything the ReadMe Connector can do

About the Connector

What ReadMe adds to your AI.

Once you connect it, your AI gains 10 capabilities: the exact actions it can take in ReadMe when you ask. The Connector page lists every one of them in detail, alongside the latency we measure in production and prompts worth trying first.

See everything the ReadMe Connector can do