Skip to content
Founding Lifetime: every Pro skillfirst 100 members · $169 onceUpgrade
Lookbk
Sign In

Lookbk MCP server

Connect Lookbk to your AI agent

Add one URL and your agent can search every Lookbk skill, read what each one makes, and hand you the exact command to install it. No API key, nothing to run locally.

https://lookbk.dev/api/mcp
Set it up See the tools
A sketch of a session: your agent asks the Lookbk server, then answers with real skills from the catalog.
Works withClaude CodeClaude CodeCodexCodexCursorCursorGitHub CopilotGitHub CopilotGemini CLIGemini CLIand any Streamable HTTP client

The fast way

Let your agent add it

Paste this into the agent you already use. It edits its own settings and tells you what to restart.

Setup prompt

Add the Lookbk MCP server to your MCP settings.
URL: https://lookbk.dev/api/mcp
Transport: Streamable HTTP. It needs no API key or sign-in.
Name it "lookbk". Then tell me what I need to restart, and list its tools once it is connected.
  • One minuteThe agent adds the server to the right settings file for itself.
  • No keys to pasteThe server is public and read-only, so there is no token to store.
  • You stay in chargeInstalls still run as normal commands your agent asks you to approve.

Set up by hand

Or do it yourself in three steps

  1. Add the server to your client

    Pick your client and copy its snippet. Each one points at the same URL.

    No API key Streamable HTTP Read-only

    One command adds the server. Add --scope user to have it in every project, not just this one.

    Terminal
    $ claude mcp add --transport http lookbk https://lookbk.dev/api/mcp

    Then: Run /mcp inside Claude Code to see lookbk listed as connected.

  2. Try a first search

    Start with a question that only searches, so you can see the tools work before anything is installed.

    Use the lookbk MCP server to find two skills for a 20-second product launch video. Don’t install anything yet.

    What good looks like: Your agent calls search_skills and answers with two launch skills, each with a lookbk.dev link and whether it is free or Pro.

  3. Install with the command it gives you

    When you pick a skill, your agent runs the Lookbk install command in your terminal. The first time, it shows you a link to approve the device on lookbk.dev; Pro skills then check your plan.

    curl -fsSL https://lookbk.dev/cli.js | node - add kinetic-title-drop
    Approve a device What Pro covers

4 tools

What your agent can do with it

Every tool only reads the catalog. The descriptions below are the ones your agent sees.

search_skills(query: stringoutput?: "video" | "slides" | "image" | …free?: booleanlimit?: integer)

“Find me a skill for a 30-second launch video.”

Search Lookbk skills

Ranks the catalog against a plain request and returns the best fits.

get_skill(slug: string)

“What does Launch Film: Porcelain need, and what do I get?”

Get skill details

Everything on a skill page, plus its install command.

list_video_skills(free?: boolean)

“Which video skills are free?”

List video skills

The whole video shelf at once, featured and newest first.

get_install_command(slug: stringagent?: "claude-code" | "codex" | "cursor" | …scope?: "user" | "project")

“Install Kinetic Title Drop into this repo for Claude Code.”

Get install command

The exact command for your agent and folder, ready to run.

Once it is connected

Things to ask

Plain requests work. Your agent picks the tool; you see the call before it runs.

  • “Search Lookbk for a skill that makes a product launch video, and tell me which ones are free.”

    → search_skills with output "video", then a short list with Pro and free marked.

  • “Compare Launch Film: Porcelain and Launch Film: After Hours. Which suits a dark-mode developer tool?”

    → get_skill on both slugs, then a side-by-side from their own descriptions.

  • “I need a pitch deck that exports to PowerPoint. What does Lookbk have?”

    → search_skills for "pitch deck" with output "slides".

  • “Install Kinetic Title Drop for Claude Code in this project.”

    → get_install_command with agent "claude-code" and scope "project", then runs it.

  • “Find a free skill for an Open Graph image for my blog posts.”

    → search_skills for "og image" with free true, which finds Editorial OG Card.

  • “List every Lookbk video skill and group them by what they are for.”

    → list_video_skills, then groups launch films, data stories and overlays.

How it fits

Search through MCP, install with the CLI

You don’t have to use MCP. Every skill page still has a copy-paste install command, and the connect prompt still works the same.

Read the guides
  1. 01

    MCP server

    Finds the right skill and the exact install command. Read-only, no sign-in.

    https://lookbk.dev/api/mcp
  2. 02

    Lookbk CLI

    Signs in and installs skills into the folders your agent reads. One file, Node 20 or newer.

    lookbk.dev/cli.js
  3. 03

    Connect page

    Where you approve the CLI the first time, with a short code it prints.

    lookbk.dev/connect

Browsing and search are free for everyone. Installing a Pro skill uses your plan; see pricing.

FAQ

MCP questions

Something else? The guides cover installing and agents in more detail.

Do I need an account or an API key to connect?

No. The MCP server is public and read-only, so there is nothing to sign in to when you add it. You only sign in when your agent installs a skill that needs it, and that happens in the Lookbk CLI, not in the MCP server.

Does the server install or run anything on my machine?

No. The four tools only read the catalog. get_install_command returns a one-line command as text; your agent shows it and runs it in your terminal with the same approval prompt as any other command.

How do Pro skills work through MCP?

Search and details cover every skill, free or Pro. When your agent runs the install command for a Pro skill, the CLI asks you to approve the device on lookbk.dev/connect and checks your plan. Nothing is charged by searching or by running the command.

How is this different from the connect prompt and the CLI?

They work together. The MCP server helps your agent find the right skill and the exact command; the CLI (curl -fsSL https://lookbk.dev/cli.js | node -) does the sign-in and the install. You can still paste an install command from any skill page without MCP.

Which clients does it work with?

Any MCP client that supports the Streamable HTTP transport, including Claude Code, the Claude apps, Cursor, Codex, VS Code and Gemini CLI. Clients that only run local servers can use the mcp-remote bridge shown under Other clients.

What does the server see, and is there a rate limit?

Only what your agent sends in a tool call, such as a search phrase or a skill slug. It is stateless: no session, no account, no cookies, and nothing is stored about the request. Fair use applies; a client that floods it may be slowed down.

Give your agent the whole catalog

One URL, four read-only tools, and every skill one command away.

Set it up Or browse the skills first