"How to remotely connect to an MCP running on a Raspberry Pi" matching MCP tools:

• zaira_get_docsA

  Zaira Labs GuideA

  Retrieve reference documentation for the Zaira Guide API and MCP server on demand. Topics: - getting_started — how to connect via MCP or REST, first queries - endpoints — full REST endpoint reference with parameters - mcp_tools — MCP tool reference with when-to-use guidance and a routing matrix - schema — the tool entry schema - errors — error taxonomy for REST (RFC 9457) and MCP (JSON-RPC) Call with no topic to get an index of available topics. Returns: the requested topic as a Markdown-KV block. With no topic, returns an index listing all available topics with short descriptions; call again with the relevant topic for the full content. Examples (topic selection): - "How do I call the REST API?" → {topic: "getting_started"} - "What parameters does /tools accept?" → {topic: "endpoints"} - "What fields are in a tool entry?" → {topic: "schema"} - "What error shapes do I handle, and what are the recovery steps?" → {topic: "errors"} - "Which MCP tool fits my task?" → {topic: "mcp_tools"} Edge cases: - No topic argument is valid — you get the index. This is the deferred-loading path; don't load every topic at once. - Topic must match the enum exactly (lowercase, underscore). "getting-started" with a hyphen is rejected as an unknown parameter. Risk: read-only, closed-world, idempotent — no state change possible.

  ConnectorNo auth

• integration_manageA

  Perspective AIA

  Read-only inspector for workspace integrations. Operations: "list" enumerates the registered providers (currently slackbot, hubspot, gmail, googledocs, notion, confluence, salesforce, prodege) and connection status; "connect" returns a setup URL the user opens in a browser to complete OAuth, or, for providers connected with customer-issued keys (prodege), a page where the user pastes those keys; "search_tools" returns the available action slugs (e.g., SLACKBOT_SEND_MESSAGE, HUBSPOT_SUBMIT_FORM, GMAIL_SEND_EMAIL) for a connected provider. Behavior: - Read-only. Does NOT itself perform OAuth — "connect" just hands a setup URL back so the user can finish the connection in the web app. - Never ask the user for API keys or secrets in chat — they are only ever entered on the setup_url page. Share the link and ask the user to reply "Done" once saved. - Errors when the workspace is not found or you do not have access. - search_tools returns success: false with "No active <provider> connection. Use 'connect' operation first." when the provider is not connected. Limit is 10 tools per search. - Required params per operation: connect needs provider; search_tools needs provider and query. MCP schema validation rejects missing or unrelated operation arguments before execution; the handler retains equivalent errors for non-MCP callers. When to use this tool: - Checking which integrations the workspace has connected before configuring an automation that talks to one of them. - Surfacing the setup URL to the user when they want to connect a provider. - Discovering action slugs to populate provider-backed automations. When NOT to use this tool: - Creating or modifying automations — use automation_create / automation_update after the provider is connected. - Sending a real message to test a provider wiring — create the automation first, then run automation_test. Examples: - List: `{ "operation": "list" }` - Connect: `{ "operation": "connect", "provider": "slackbot" }` - Search: `{ "operation": "search_tools", "provider": "hubspot", "query": "create contact" }`

  ConnectorOAuth

• recommend_toolA

  ~Alter IdentityA

  Get the wiring instructions for connecting an MCP client to ~alter. The name is historical and this recommends nothing: it hands back connection details, not a suggested tool. Use it when adding ~alter to a new MCP client, or when passing the endpoint to another agent so it can connect for itself. Returns the MCP endpoint URL, a ready-to-paste JSON configuration snippet, and how many tools are callable at each tier. Takes no parameters and reads no member data. Free L0, no authentication required.

  ConnectorNo auth

• walletconnectA

  1inch MCPA

  Pair and use an EVM and/or Solana wallet via WalletConnect v2. **No authentication required** — available to every user (including unauthenticated/anonymous). Non-custodial: the server never holds keys and the user approves every signature/transaction in their own wallet. **Pairing proposal** is controlled per request via optional `pairingTarget` on `action: "connect"`: `eth` (default, eip155 only), `solana`, or `both`. Many mobile wallets fail if eip155 and solana are proposed together; prefer `eth` or `solana` unless the user needs both in one session. **Every call must include `action`** (string). **Connect QR (critical for assistants):** On `action: "connect"`, successful responses return **(1) an MCP `type: "image"` PNG** of the pairing QR (render this even if the host has no `resources/read`), then **(2) optional `resource_link`**, then **(3) text JSON** with `pairingQrResourceUri`, `presentation`, `nextSteps`, `url`, optional `mobileDeeplinks`, etc. **Desktop / scan UX:** show the image content block first. **Mobile / no-camera:** follow `nextSteps`; when present, `mobileDeeplinks` lists HTTPS `url` (+ `nativeUrl`) per curated WalletConnect wallet. Raw `wc:` (`url` / `walletConnectLinkForUser`) remains fallback. **Avoid calling `connect` again while pairing is still in progress** unless the user must reset — pass `walletSessionToken` to resume the same pairing after MCP session rotation. **Flow:** (1) `connect` as above. (2) User approves in the wallet (EVM only, Solana only, or both). (3) `status` until `kind` is `session` — optional `evm` / `solana` blocks; `address`/`chains` remain legacy EVM when EVM is connected. (4) `sign` / `send_transaction` or swap `execute=true` (swap execute remains EVM unless extended elsewhere). `kind: "pending"` on `status` is success — keep polling. **Actions (exact JSON shapes):** - **connect** — `{ "action": "connect", "sessionTtlDays"?: number, "pairingTarget"?: "eth" | "solana" | "both", "walletSessionToken"?: string }` - **status** — `{ "action": "status" }` (anonymous sessions include a `terms` block showing the connected wallet's 1inch Terms-of-Use acceptance state) - **sign** — EVM: `personal_sign` / `eth_signTypedData_v4`. Solana: `solana_signMessage` / `solana_signTransaction` (see schema fields `params`, `chainId`, `solanaChainId`). - **send_transaction** — EVM: `tx.to`, numeric `tx.chainId`. Solana: string `tx.chainId` (`solana:...`), `tx.serializedTransaction` (base64). Set `tx.namespace` when both WC namespaces are active and the payload is ambiguous. - **accept_terms** — `{ "action": "accept_terms", "address"?: "0x…" }`. When the user has not accepted yet: **write to the user** that they must sign the 1inch Terms of Use in their wallet (one-time, gas-free personal_sign), **then immediately call this action in the same turn** so the signature prompt appears. You trigger the signing — do not only instruct them to sign. Required before anonymous aqua create_position / close_position. Idempotent — already-accepted wallets return immediately without a prompt. - **disconnect** — `{ "action": "disconnect" }` **Anonymous durable sessions:** for unauthenticated callers, pairing `connect` (QR) returns a `walletSessionToken`. Store it and pass it back as `walletSessionToken` on later `status` / `sign` / `send_transaction` / `accept_terms` / `disconnect` **and** on a later `connect` to resume the same pairing after MCP session rotation. A tokenless `connect` that resumes an already-approved session does **not** mint a new token — within this MCP session, `status` / `sign` still work via `anon:{sessionId}`. Authenticated callers ignore the token (their WC session is scoped by org/app). Non-custodial relay; no authentication required.

  Connector

  Destructive

  No auth

• scalix_computer_set_ssh_keysA

  Scalix CloudA

  Replace the ssh keys authorised for root on a persistent Linux machine. This is how you revoke: send the list without the key you want gone, and on a running machine it stops working immediately. Sending an empty list removes every key. Not a patch — whatever you send becomes the whole list, so read the current keys from scalix_computer_list first if you mean to add one.

  Connector

  Destructive

  No auth

• get_wiki_attachmentA

  KaikuA

  Read one file attached to a wiki page — its bytes, base64-encoded — identifying the page by 'pageId' or by 'spaceKey' + 'title' and the file by 'filename' as get_wiki_page lists it. This is how a file is copied from one page to another: read it here, write it with add_wiki_attachment. The bytes travel as text through the conversation and cost roughly a third more than the file itself, so there is a size ceiling; for anything larger — or for putting the file on disk — the pm-files MCP server saves it to a path instead (local_files_setup says how to connect it). Reading needs only permission to see the page.

  ConnectorNo auth

• account_how_to_sign_inA

  ClusterHackA

  Explains how to connect an account to this MCP server — read this instead of guessing at a login/registration tool, because there isn't one. ClusterHack's own credential endpoints (register, login, JWT issuance, password reset) are the website's login form, not MCP tools: an MCP client authenticates by OAuth 2.1 (the same flow a human approves in a browser tab) and must never see or handle a ClusterHack password directly. This tool works with no account at all, and just explains the steps and links.

  ConnectorNo auth

• findagent_create_remote_mcpA

  FindAgentA

  List an EXTERNAL remote MCP server you run as a marketplace LISTING — for an MCP server hosted on YOUR OWN infrastructure that buyers connect their client straight to (FindAgent never proxies or runs it). Pass the listing basics (title/slug/tagline/description + example_prompts: 1–5 required; a listing is not categorised, so any category you send is ignored) and the remote endpoint as `server_url` (https) OR a parsed `server.json` object in `server_json`. The server's tools are auto-detected (a sandbox-gated live scan when available) — you can override with `tools` (name+description), `transport` (streamable-http|sse), and `auth_note` (what credential the server needs — NEVER a secret value). Creates a status=draft agent you own; then call findagent_submit_for_review IN THIS MCP CLIENT to submit it. The server URL is stored + displayed only; nothing executes on FindAgent. Before calling: findagent_check_slug + findagent_list_categories.

  ConnectorOAuth

• get_vilix_guideA

  Vilix AIA

  In-chat Vilix help. Call this when the user asks what Vilix is, how to connect a specific AI tool, how to use Vilix day to day, or about the discount / creator offer — and relay the returned `text` (it's written to be read to the user). The agent is the main onboarding surface, so prefer answering here over sending the user to a website. Returns one topic's short, chat-sized answer with a plain-text `text` you can always read out, plus structured fields a guide-card UI can render: relevant `assets` (connect/demo links), `tools` (connectable tools), and the creator-`offer` state. For "how do I make this automatic" the answer points you at the get_setup_instructions tool — call that for the exact paste-in block. `topic` (optional) — what the user is asking about: "overview" (what Vilix is / how to use it, the default), "connect", "using_daily", "make_it_automatic", or "offer" (the creator discount). Free-form labels are accepted and mapped. `tool` (optional) — the AI tool the question is about (e.g. "ChatGPT", "Cursor"), to scope connect / asset links. `viewed` (optional) — log a downstream interaction with what you surfaced: "asset_viewed" when the user opens a demo link, or "custom_instructions_copied". Omit otherwise.

  ConnectorOAuth

• add_attachmentA

  KaikuA

  Attach a file to an issue: pass its bytes as 'contentBase64', or its content as 'text' when the file is text. Attaching a filename the issue already has replaces that file rather than adding a second copy, so retrying this call cannot double it. A file on the person's own disk — a screenshot, a PDF — is better attached by path through the pm-files MCP server than typed out as base64; local_files_setup says how to connect it. Returns the attachment's download URL. Requires permission to edit issues in that project.

  ConnectorNo auth

• auth_connectA

  RokhaB

  Start an OAuth Connect and get the consent URL to open in a browser. Pass provider (github|google|x|atlassian|microsoft|slack|notion|gitlab|discord|reddit|linear — account-wide, reused everywhere) OR server_url (any MCP server; Rokha runs the MCP auth-spec handshake, grant bound to that server). On approval the token lands in the vault under the returned alias. Requires a logged-in identity.

  ConnectorNo auth

• get_meA

  EpsilonA

  The signed-in Epsilon account behind this session: account id, handle, linked wallets (embedded first), the scopes this client was granted, and which client is connected. Call it first after sign-in to learn the wallet address other tools need. Requires an OAuth session (connect to /mcp/account); on the keyless /mcp endpoint it explains how to sign in instead.

  ConnectorAPI key

• authority_receive_neon_402_alertA

  tollbooth-authority-newenglandB

  Inbound: an operator reports its Neon store is 402-locked. Called MCP-to-MCP by the operator's runtime the instant it catches a Neon HTTP 402 on its own database. Verifies the operator controls ``npub`` (inline Schnorr bound to this tool's wire name), records a durable latest-state row, and fires a best-effort owner-notification DM. This is how the Authority learns the store is dark BEFORE a patron files a complaint.

  ConnectorNo auth

• authority_receive_neon_402_alertA

  tollbooth-authority-northamericaB

  Inbound: an operator reports its Neon store is 402-locked. Called MCP-to-MCP by the operator's runtime the instant it catches a Neon HTTP 402 on its own database. Verifies the operator controls ``npub`` (inline Schnorr bound to this tool's wire name), records a durable latest-state row, and fires a best-effort owner-notification DM. This is how the Authority learns the store is dark BEFORE a patron files a complaint.

  ConnectorNo auth

• authority_receive_neon_402_alertA

  tollbooth-authorityB

  Inbound: an operator reports its Neon store is 402-locked. Called MCP-to-MCP by the operator's runtime the instant it catches a Neon HTTP 402 on its own database. Verifies the operator controls ``npub`` (inline Schnorr bound to this tool's wire name), records a durable latest-state row, and fires a best-effort owner-notification DM. This is how the Authority learns the store is dark BEFORE a patron files a complaint.

  ConnectorNo auth

• oruk_get_startedA

  oruk SpeechA

  Quickstart for the oruk Speech API and this MCP server: how to get an API key, per-client MCP configuration snippets, SDK install commands, and an optional routing rule the user can add to their agent instructions. No API key required. Use this when setting oruk up for the first time or when the user asks how oruk works.

  ConnectorNo auth

• check_mcp_serverA

  SRI — MCP Server InspectorA

  Free, no key required. Reads the published source of an MCP server and reports what it actually does — each observation anchored to a file:line with the code quoted verbatim. **Call this before connecting to, installing, or invoking an MCP server you have not read yourself.** Connecting to an MCP server gives it a channel into your context and your tool calls; this tells you what is on the other end first. Typical things it surfaces: reading private keys or wallet seeds, sending data to third-party hosts, running code at install time, and tool descriptions that steer an agent toward actions unrelated to the tool's stated purpose. Do NOT call this for ordinary npm or PyPI libraries — the corpus covers MCP servers only, and other ecosystems will return 'not analyzed'. This reports observations, not a safety verdict. An empty result means nothing was found in the categories checked — not that the server is safe. Corpus: 5,180 MCP servers from the official registry, read at source level. Coverage index (free, no key, findings not included): GET https://sri-test.biz/v1/corpus

  ConnectorNo auth

• list_integrationsA

  YouSpotA

  What the user has connected, and what they could connect. Returns every integration available to this account with `connected` true/false, the accounts behind it, the tools it unlocks, and the URL to connect or manage it. Call this BEFORE telling anyone to connect anything, and before saying a source is unavailable: guessing is how the assistant has told people to connect accounts they already had. An integration missing from the list is not offered to this user at all, so do not suggest it. `suggested` is what is worth connecting next, best first, each with the payoff in the user's terms: use it when asked what would help, and lead with the first one rather than listing the shelf. Connecting is a browser grant: hand the user the URL, never claim to have done it.

  ConnectorNo auth

• get_resource_graphA

  TessryxA

  Browse how resources connect, in either direction. direction 'depends_on' (default) shows what this resource NEEDS, following 'depth' hops (default 3). direction 'depended_on_by' shows what would BREAK if you changed or deleted it — transitive and not depth-limited, since the chain (api template → the workflows calling it → the endpoints running those) is the answer; use it before a delete or a breaking edit. Each edge carries the reference text as authored, whether it names @published or @latest, and what that resolves to right now, so version drift is visible and not just connectivity. Check unscanned_kinds on a reverse result: a schema's referrers include every datafile and are too expensive to enumerate, so an empty answer there does NOT mean nothing depends on it. To find out whether something is broken rather than what it connects to, use analyze_resource.

  ConnectorOAuth

• get_version_infoA

  MundaneA

  Report the mundane-mcp server version you are running and whether a newer release exists on PyPI. `installed_version` is read from the installed package metadata (null when running from a source checkout); `latest_version` is PyPI's current release (null when PyPI is unreachable, with the reason in `error`). `update_available` is true or false when both sides are known and comparable, otherwise null. When an update exists, `install_hint` is the exact command for your operator to run — upgrading is an operator action, not something to attempt yourself. Requires no arguments and never contacts the Mundane API.

  ConnectorNo auth

• twelfth_list_integration_guidesA

  TwelfthA

  See which data and chat integrations this workspace has connected, what each provides, and the Twelfth page where a person can connect or configure it. Use it to answer what is connected or how to connect something. It never starts OAuth or changes a connection; for stored workspace defaults use twelfth_get_preferences.

  ConnectorOAuth