Skip to content

Docs Connect

Use fixvis from Claude Code, Codex or ChatGPT

The fixvis MCP server lets your own AI assistant read your issues, fix them in your code, move them on the board, verify them and draft content. Available on Starter and above.

A Claude Code session that adds the fixvis MCP server, lists open technical issues for gorusmeyap.com and moves one to In progress
fixvis in Claude Code. Sample: gorusmeyap.com.

Server address: https://api.fixvis.ai/mcp

Claude Code

  1. Add the server

    claude mcp add --transport http fixvis https://api.fixvis.ai/mcp
  2. Sign in

    Run /mcp, choose fixvis and select Authenticate.

  3. Approve access

    In the browser, sign in, pick the organisation, tick the projects this connection can use, choose an access level and select Approve.

  4. Check it

    /mcp shows fixvis as connected. There is no token to copy.

Codex

  1. Add the server

    codex mcp add fixvis --url https://api.fixvis.ai/mcp
  2. Sign in

    Complete the same browser sign-in and approval.

    codex mcp login fixvis
  3. Check it

    codex mcp list

ChatGPT and other MCP clients

In ChatGPT, turn on Developer mode in settings, then add fixvis as a connector with the server address above. Any other client that supports remote MCP servers over HTTP, such as Cursor, connects to the same address.

Access levels

LevelWhat the assistant can do
Read your fixvis dataRead-only: issues, markets, competitors, content gaps, outcomes
Read and updateAlso move issues, verify fixes, create content tasks and record published URLs. Scans and content generation still ask you to confirm

Tools

ToolAccessWhat it does
list_projectsReadProjects in this connection, with latest audit and open issue counts
list_issuesReadA project's issues, worst first, filtered by area, severity and status
get_issueReadEverything needed to fix one issue: evidence, affected URLs, how it's re-checked
explainReadAn issue or term in plain language, and why it matters
move_issueWrite, freeMove an issue to To do or In progress, or mark it shipped
verify_fixWrite, freeRe-check the live page and return the outcome with evidence
list_marketsReadTracked markets, the primary one, and each one's latest scan
get_market_visibilityReadOne market's AI visibility score, trend, citations, issues, and the questions you win or lose
get_markets_rollupReadAll markets side by side
list_competitorsReadTracked competitors in one market and where you stand
list_content_gapsReadContent opportunities in one market, ranked
get_content_gapReadOne opportunity in full: keywords, competitor URLs and a brief
create_content_taskWrite, freeAdd a content piece to the board, from a gap or a topic
generate_contentWrite, uses a fixWrite a brief or draft for a content task
get_contentReadA generated brief or draft, or its status
set_published_urlWrite, freeRecord the live URL of a published piece so fixvis can measure it
get_outcomesReadWhat fixes and content achieved over a period
list_delivered_fixesReadFixes and content delivered in a period, with outcomes
get_fix_outcomeReadOne delivered fix's before and after
run_market_scanWrite, uses a fixScan one market or all markets

Anything that uses a fix asks first

generate_content and run_market_scan work in two steps. The first call returns a preview of the cost and your balance, and nothing is spent. Only when you agree does the assistant call again to run it. A failed draft is not charged. Today's included scan of each market is free.

Things to ask

  • “Use fixvis to show the open technical issues for gorusmeyap.com, worst first.”
  • “Get the full details of the top issue and find where in this repo it comes from. Don't change code yet.”
  • “Apply the fix, then move that issue to In progress in fixvis.”
  • “I've deployed. Verify that fix with fixvis.”
  • “What should we write next for Germany?”
  • “How did last month's fixes do?”