Sneak Peek: okl.ink Model Context Protocol (MCP)
A preview of how okl.ink is designing hosted MCP integration to let AI assistants build and style pages programmatically.
Coming Soon & Active Development
The okl.ink MCP server is currently in internal preview. Endpoint behavior, authentication schemas, and tool specifications are undergoing testing before official public release.
We are building Model Context Protocol support into okl.ink. With a hosted MCP server over streamable HTTP, AI assistants like Claude, Cursor, and Windsurf will soon be able to scaffold pages, attach repositories and live demos, set themes, and publish directly from natural language prompts.
Because the server runs directly on okl.ink infrastructure, you will not need to manage local Python bridges or npm packages. Your scoped API token ensures secure, fine-grained access control.
Planned tool capabilities
The server maps directly to core page and link operations:
- create_page — scaffold a new project with title, custom slug, theme, and initial links
- list_pages / get_page — query your existing pages and check link metrics
- update_page — update title, description, slug, and cover images
- add_link — attach live demos, GitHub repositories, docs, social embeds, and media
- set_theme — configure presets (oklink, midnight, paper, vivid, lofi), typography, and density
- publish_page — toggle live visibility
- validate_link — verify target destination security before adding
Architecture: Streamable HTTP
Rather than requiring STDIO processes running on local builder machines, okl.ink MCP communicates over JSON-RPC 2.0 over HTTP. Requests carry standard bearer tokens verified server-side against SHA-256 hashes.
What to expect next
We are fine-tuning tool signatures, error resilience, and agent workflows. Stay tuned for public rollout announcements!