AI Integration

GitResume speaks MCP, the open standard for connecting AI assistants to outside services. Once connected, your assistant can migrate a PDF resume to GitResume, read your resume, check how your last push built, hand you a download link, and publish, all without you switching back to the dashboard.

It works with Claude and any MCP-compatible client, on the free plan too.

Connect

The GitResume MCP server uses Streamable HTTP and authenticates with OAuth dynamic client registration, so there is no client ID or token to request beforehand:

https://gitresume.co/mcp

GitResume is also listed in the official MCP registry as co.gitresume/gitresume.

Claude (web and desktop)

GitResume is listed in Claude's connector directory. Open GitResume in the Claude directory, click "Connect to Claude", and approve on the GitResume authorization screen.

Once connected, the button changes to "Connected".

Add it manually as a custom connector

If you can't see the directory, or your organization's admin restricts it, add GitResume by hand: open Settings → Connectors → Add → Add custom connector, enter GitResume as the Name and https://gitresume.co/mcp as the MCP server URL, click "Continue", and approve on the authorization screen.

Claude Code

1. Run this in your terminal:

   claude mcp add --transport http gitresume https://gitresume.co/mcp

2. Open Claude Code and run /mcp to authorize.

Codex

The desktop app and the CLI share one configuration, so either one works.

• Desktop: open Plugins → MCPs → Add → Add MCP server, name it gitresume, set Type to Streamable HTTP, enter the URL above, leave the other fields empty, and save. Then click Authenticate on the gitresume row to authorize.
• CLI: run

  codex mcp add gitresume --url https://gitresume.co/mcp
  codex mcp login gitresume

Other clients

Any tool that supports remote MCP servers can use the URL above as a Streamable HTTP server; your browser opens to authorize on first connect. For tools that take a JSON configuration:

{
  "mcpServers": {
    "gitresume": {
      "url": "https://gitresume.co/mcp"
    }
  }
}

Permissions

You decide what to grant on the authorization screen, and read access alone is a valid choice:

An assistant only sees what you granted. Withhold Publish and the publishing tools do not exist for that connection at all. Review and revoke your connections anytime under Profile → Connected Agents; a revoked connection stops working within 15 minutes.

What you can ask for

No tool names to memorize. Just say what you want:

• "Migrate this PDF resume to GitResume." Converts it, validates it, creates the project, and builds it.
• "Did my last push build?" Reads the latest build, and if it failed, brings back the error so you can fix it.
• "What should I fix in my resume?" Reads the Resume Check reminders from the latest build, with the lines to edit.
• "Tighten the margins so my resume fits on one page." Adjusts the layout density, rebuilds, and checks the result again.
• "Check this resume against the schema before I push." Validates the YAML, so a typo costs seconds instead of a failed build.
• "Give me the PDF link." Returns a download link to open in your browser.
• "How many people viewed my resume this month?" Reads the same analytics the dashboard shows.
• "Publish it." Flips the resume live and returns the public URL.

Importing an existing resume

If you already have a resume in any format (PDF, Word, Markdown, and more), this is the fastest way: create a GitResume account, connect your AI tool (Claude, Claude Code, Codex, and so on) to the GitResume MCP server with the Write permission, then hand it the file and ask it to migrate the resume to GitResume. It converts the format, gets it through validation, confirms the URL with you, then creates the project and builds it, all inside the conversation. The new resume is not public by default; ask the assistant to publish it once you are happy with it.

When it finishes, the project is in your GitResume dashboard, where you can download the PDF, keep editing, or click "Publish".

On the left is the original PDF handed to the assistant; on the right, the version GitResume built:

Troubleshooting

Privacy

Authorizing an assistant lets it access the data and actions you granted, acting as you, until the authorization is revoked. Once data reaches that assistant, how it is handled is governed by its provider's privacy policy, not ours. To end it, revoke the connection under Profile → Connected Agents. Full terms are in the AI Assistant Authorization section of the Privacy Policy.