Claude Code MCP Integration

Flint has an MCP (Model Context Protocol) server that connects directly to Claude Code. Once connected, you can create landing pages from your terminal just by describing what you want.

This integration allows Claude Code to create, modify, and manage your Flint pages directly through conversation in your development environment.

Run this command in your terminal to add Flint as an MCP server:

claude mcp add flint --transport http https://mcp.tryflint.com/mcp

This adds Flint as a remote HTTP MCP server that Claude Code can use to build and manage your landing pages.

After adding the server, authenticate with your Flint account:

1. Open the MCP menu in Claude Code

/mcp

2. Select Flint and authenticate

Follow the prompts to sign in to your Flint account in your browser. This authorizes Claude Code to create and modify pages on your behalf.

Confirm the server was added correctly:

claude mcp list

You should see flint in the list of configured servers. To get more details:

claude mcp get flint

Once connected, you can ask Claude Code to build landing pages for any campaign, ICP, or keyword. Describe the audience, the offer, and the tone - Claude Code handles the rest and builds the page directly in Flint, ready to publish.

Example Prompt

Generate a personalized account page targeting Anthropic. Tailor the messaging to address their specific industry needs.

Claude Code will use Flint to generate and create the page, which you can then preview and publish.

The Flint MCP server exposes four tools that Claude Code can use:

run_background_agent

Start a background AI agent on a Flint site. The agent executes a prompt to modify your website.

Returns a workflow ID that can be used to check status.

check_background_agent_status

Check the status of a previously started background agent.

Returns the current status, phase, and output when completed.

list_sites

Lists all Flint sites accessible to your account. No parameters required.

Returns a list of sites with their name, site ID, organization ID, and organization name. This is useful for discovering your site IDs without leaving the conversation - just ask Claude Code "what sites do I have?" and it will look them up for you.

publish_site

Deploys a Flint site to production.

Resolves the latest changes on the staging branch and triggers a production deployment. This lets you go from editing to live in one conversation - ask Claude Code to make changes with run_background_agent, then publish them with publish_site.

You can control where the MCP server configuration is stored using the --scope flag:

# Local scope (default) - only you, only this project
claude mcp add flint --transport http https://mcp.tryflint.com/mcp

# User scope - available to you across all projects
claude mcp add flint --transport http --scope user https://mcp.tryflint.com/mcp

# Project scope - shared with everyone via .mcp.json
claude mcp add flint --transport http --scope project https://mcp.tryflint.com/mcp

Use these commands to manage your Flint MCP server:

# List all configured servers
claude mcp list

# Get details for the Flint server
claude mcp get flint

# Remove the Flint server
claude mcp remove flint

# Check server status in Claude Code
/mcp

Connection not working?

1. 1.Verify the server URL is entered exactly as shown above
2. 2.Try removing and re-adding the server: claude mcp remove flint then add it again

Authentication issues?

1. 1.Run /mcp in Claude Code and select "Authenticate" for Flint
2. 2.Complete the browser login flow
3. 3.If the browser redirect fails, copy the callback URL from your browser and paste it into Claude Code

Pages not appearing?

1. 1.Check that the task completed successfully in Claude Code's response
2. 2.Refresh your Flint dashboard to see newly created pages
3. 3.Verify you have the correct Flint site selected