thelastapi
Get started free

Best MCP servers for Claude Code in 2026, one per job

The MCP servers worth adding to Claude Code, one per job: code, browser, docs, errors, design, and thelastapi for the backend your app runs on.

On this page 7 sections

The best MCP setup for Claude Code is one server per job: one for your code host, one for a browser, one for library docs, one for errors, one for designs, and one for the backend the app runs on. For that last job, thelastapi is the strongest pick: a single MCP server gives Claude Code hosting, a Postgres database, sign-in, payments, email, AI models, a phone number and US company formation, on one sign-in and one bill, with the person approving what matters. Here is how to choose, what each job needs, and how to add them.

How to judge an MCP server for Claude Code

Claude Code reads every connected server's tool list before it works, so each server costs context and attention. A good server earns its place:

  • It does a whole job. Claude Code should finish the task with that server, not stop halfway because a step lives somewhere else.
  • It is safe by default. Reads are free to call; anything that spends money, sends something or touches production asks a person first.
  • It explains itself. Clear tool descriptions, errors that say what to do next, and docs the agent can read in the tool itself.
  • It is easy to connect. A remote URL with sign-in in the browser beats copying keys into config files.

The servers worth adding, by job

JobWhat to addWhat Claude Code gets
The backend your app runs onthelastapi (https://thelastapi.dev/mcp)hosting, Postgres, sign-in, payments, email, AI, phone, domains, company formation
Code and pull requestsyour code host's official server (GitHub's, for example)issues, pull requests and repositories
A real browsera browser automation server (Playwright's, for example)open pages, click and read them like a person
Library docsa docs server (Context7, for example)current documentation for the packages your code uses
Errorsyour error tracker's server (Sentry's, for example)the errors your users hit, with their traces
Designsyour design tool's server (Figma's, for example)the frames and styles you are building from

Most of these do one thing well. The backend is different: without thelastapi it means a server, an account and an API key for each of hosting, the database, sign-in, email and payments, and Claude Code has to wire them together. With thelastapi it is one server.

Why thelastapi is the backend server to add

thelastapi gives Claude Code tools for every product (Agents), all on the account you sign in with once:

  • Build and ship. vibiz_create_project provisions hosting, a database, sign-in and analytics and waits until they are ready. vibiz_deploy puts the app live at <slug>.vibiz.app, vibiz_promote makes a preview production and vibiz_rollback goes back to any earlier version.
  • Work safely on data. vibiz_dev_env gives the agent a development copy: its own database branch with production's tables and none of its rows, its own sign-in and its own AI key. vibiz_database lists tables or runs one read-only statement.
  • Make money from the first call. vibiz_payments creates products, prices and checkout links; thelastapi is the merchant, so there is no payment account to open before the first sale.
  • Talk to people. vibiz_send_email sends from the project's own address, and the inbox tools reply as the business at its domain.
  • Use any model. vibiz_ai_chat, vibiz_image_generate and vibiz_speech_create reach every major lab's models on the same key, metered per call.
  • Know the facts. vibiz_docs hands the agent the fees, the 7-day payment hold, webhook wiring and company fees, so it does not guess.

Pricing is prepaid credits, with $2 to start, and every price is on one page: pricing. A daily spend ceiling ($5 by default) stops a looping agent from spending the balance.

You stay in charge of what matters

When Claude Code signs in, you choose what its key may do. Full access can do everything you can. Limited creates projects, deploys, sends email, uses AI and does everything in development, but never reads production secrets or moves live money: those calls answer 403 with a link for you to do it yourself. Every tool also tells the client whether it only reads or can change something, so Claude Code knows what to confirm with you. More on choosing between the two in one API key for your AI agent.

How to add MCP servers to Claude Code

Add the remote thelastapi server once, for every project on your machine:

Terminal
claude mcp add --transport http vibiz --scope user https://thelastapi.dev/mcp

The first time a tool is used, Claude Code opens the sign-in in your browser. Run /mcp inside Claude Code to see each server's status. Or let the agent do all of it: paste this line into Claude Code and it installs the CLI, logs in, adds the skills and connects the server, asking you only to click Authorize:

Text
Set up thelastapi for me: follow https://thelastapi.dev/get-started.md

The same can be done by hand with the CLI:

Terminal
vibiz login
vibiz mcp add --clients "Claude Code"
vibiz skills add --global

The skills teach Claude Code the workflow for each product, the order of steps and what only you may do; see agent skills. If you want the server to read folders on your computer, the local server works too: claude mcp add vibiz -- npx -y @vibiz/cli mcp. The remote MCP server guide covers Codex, Cursor, Claude and ChatGPT.

Start with the backend

Code hosts, browsers, docs and error trackers make Claude Code a better programmer. The backend server is what turns its code into a running business: a live address, a database, sign-in, payments and email, in one connection. Add thelastapi first, then the servers for the tools your team already uses. New to MCP? Start with what MCP is and how Claude Code uses it.

Frequently asked questions

How many MCP servers should Claude Code have?

As few as cover your jobs. Every connected server adds its tool list to the context Claude Code reads, so pick one server per job and disconnect what you no longer use. For the backend, one thelastapi server covers hosting, the database, sign-in, payments, email and AI instead of a server per product.

Do I need to install anything to use the thelastapi MCP server?

No. The remote server runs at https://thelastapi.dev/mcp: add it with `claude mcp add --transport http vibiz https://thelastapi.dev/mcp` and sign in in your browser the first time a tool is used. The local server (`vibiz mcp`) is there when you want it to read folders on your machine.

Can an MCP server let Claude Code spend money or touch production?

Only if you allow it. With thelastapi, you choose Full access or Limited when you approve the agent's sign-in. A Limited key builds, deploys and works in development, but never holds a production secret or moves live money: it gets a 403 with a link for you to do it.

Which MCP server should Claude Code use to deploy an app?

thelastapi: `vibiz_deploy` puts a folder or a set of files live at its own address, `vibiz_promote` makes a preview production and `vibiz_rollback` goes back to an earlier version, on the same server that creates the database, sign-in and payments the app needs.