Profile
Read and update your display name and bio without exposing account settings.
Compatible with:
Connect in one prompt
This tells your agent which endpoint, transport, and authentication header to configure. Replace the example key with a personal key from your Biolinky settings.
Set up Biolinky as a remote MCP server for this agent.
Server name: Biolinky
URL: https://biolinky.co/api/mcp
Transport: Streamable HTTP
Authentication header: Authorization: Bearer YOUR_BIOLINKY_API_KEY
Store the API key in this client's secure secret store, keychain, or an environment variable named BIOLINKY_API_KEY when supported. Never commit it to source control, write it to logs, or echo the full key back to me.
After setup, test the connection by listing the available Biolinky tools. Do not change my Biolinky page until I explicitly ask you to. If you cannot configure MCP servers directly, show me the exact secure command or configuration for this client instead.The public example contains only a placeholder. Paste a completed prompt only into a trusted private agent, or use OAuth for hosted and third-party agents.
Read and update your display name and bio without exposing account settings.
Create, edit, reorder, archive, and restore links with conflict protection.
Manage social profile destinations while staying bound to your page.
Read up to 30 days of analytics, with detail following your Biolinky plan.
Never exposed: billing, subscriptions, email, passwords, verification, plan controls, tracking pixels, or permanent deletion.
Recommended
https://biolinky.co/api/mcp in a remote MCP client.Scripts and header-based clients
Create a page-bound key in your settings and send it only in the Authorization header. The full secret is shown once.
curl https://biolinky.co/api/v1/page \
-H "Authorization: Bearer blky_live_…"REST reference: OpenAPI 3.1 document
Safety by design
Guides and use cases
Learn how MCP gives AI agents a structured, permissioned link-page interface.
Design useful agent workflows with human review and narrow access.
Build direct REST integrations for apps, scripts, and internal tools.
Keep client campaign destinations current without sharing passwords.
Turn virtual creator profile visits into a focused, measurable next step.
Plan a consistent persona, repeatable content system, and ethical funnel.