Browse docs MCP server

Connect AI assistants

Let Claude, ChatGPT or another MCP client create drafts, check analytics and read form responses in your Walink account.

Updated November 11, 2026 View as Markdown

Walink's MCP server lets an AI assistant work in your Walink account. Ask Claude to draft a link for your next campaign, ask ChatGPT how last week's clicks compare with the week before, or ask any MCP client to list the newest responses to a form. The assistant follows the app's rules: it builds drafts, which are private and free, and it can only do what you allowed when you connected it.

The server address:

https://mcp.walink.com/mcp

What the assistant can do

Ask it to Tools
Read your account, allowance and free links walink_get_account
Find a link, Smart Link, form or Multilink page walink_search, walink_list_resources, walink_get_resource
Check that an address is free walink_check_handle
Say what a draft still needs before publishing walink_check_publish_readiness
Report analytics, by country, source, device and more walink_get_analytics, walink_get_analytics_breakdown
Give you the address to share and the QR code's target walink_get_share_kit
Read the responses to a form walink_list_form_responses
Draft a Premium Link, Smart Link, form or Multilink page walink_create_link_draft, walink_create_smart_link_draft, walink_create_form_draft, walink_create_multilink_draft
Edit them walink_update_link, walink_update_smart_link, walink_update_form, walink_update_multilink
Style a QR code walink_set_qr_style
List, read, create and delete free links walink_list_free_links, walink_get_free_link, walink_create_free_link, walink_delete_free_link
Publish, unpublish or delete walink_publish, walink_unpublish, walink_delete

The server also offers six ready-made prompts, such as a weekly performance report, a lead form and a review of your drafts. Each ends in a draft or a report, and stops before publishing.

Claude, ChatGPT and other clients that support MCP sign-in (OAuth) need no token: you sign in to Walink and choose what the assistant may do.

In Claude

  1. In the Walink app, open Developers from the account menu and select Connect with Claude, under MCP Setup. Claude opens its dialog to add a custom connector, with Walink and the server address filled in. You can also add a custom connector in Claude yourself, with the address above.
  2. Confirm it in Claude, then sign in to Walink when Claude sends you there.
  3. Choose the permissions on the consent screen and select Allow.

The connection then works on Claude's web, desktop and mobile apps.

In ChatGPT

Add a custom connector in ChatGPT's settings with the server address and OAuth sign-in. ChatGPT then sends you to Walink to sign in and approve. Where that setting lives, and which ChatGPT accounts have it, is up to OpenAI: their help center has the current steps.

Walink asks whether to allow the app (by its name) to use your Walink account, shows the account you're signed in with and the address you'll return to. Under What it can do, the permissions the assistant asked for start ticked, except the high-risk ones: Publish, Delete and Form responses stay off until you turn them on.

  • To let the assistant publish, create free links or edit what's already live, tick Publish under Links, Forms or Multilink.
  • For an assistant that only reads, select Read only under Quick presets.

If Walink can't verify the app, the screen says so: continue only if you started the connection yourself.

Connect with an API token

Claude Code, Cursor, VS Code and other clients that can send a header connect with a personal token instead. Create one on the Developers page, as in REST API, with only the scopes the assistant needs. One token works for the REST API and the MCP server, with the same scopes on both.

In Claude Code:

claude mcp add --transport http walink https://mcp.walink.com/mcp --header "Authorization: Bearer <token>"

Any other client sends Authorization: Bearer wlk_live_... to the server address. The Developers page has ready-made settings for Cursor and VS Code under MCP Setup. Keep the token in the client's settings, and never paste it into a chat.

What it can and can't do

  • Drafts by default. Every create makes a private draft, except a free link. A draft never publishes itself.
  • You decide what goes live. Publishing uses your allowance and reaches the public. Walink's tools tell the assistant to publish, unpublish, delete or create a free link only when you ask in your own words. Publish and Delete start off, and while they're off the assistant gets an insufficient_scope error instead.
  • Free links go live at once. Creating one needs Publish under Links. Its address is random, it can't be edited afterwards, and an account holds up to 5.
  • Edits to published items are live. Changing a published link, form or page changes what visitors see right away, so it needs Publish too.
  • Addresses are permanent. Confirm the spelling before the assistant creates anything: an address can't be changed after the item is created.
  • No billing. The assistant can't buy allowance, change your subscription or manage tokens. Analytics need a subscription, as in the app.

Disconnect

  • A connected app: on the Developers page, under Connected apps, select Disconnect. It stops working within 30 seconds.
  • A token: under API Tokens, select Revoke. Anything using it stops within 30 seconds.

Every endpoint and field behind these tools is in the API reference.