Coding agent documentation index Fetch the complete documentation index at: https://docs.worklittle.com/docs-agent-manifest.json Use this file to discover all available pages before exploring further.

REST vs MCP in plain English

Two ways developers and AI tools connect to Worklittle.

You may hear these two words from a developer or an AI tool. Here is what they mean without the jargon.

REST, in one line

REST is the way a program asks Worklittle for something directly. A developer writes code that says "give me software jobs in Austin" and gets a structured answer back.

Choose REST when someone is building software, such as a careers page, a dashboard, or a sync into another system.

MCP, in one line

MCP is a way to plug Worklittle into an AI assistant so the assistant can look things up itself. You connect it once, then ask the assistant questions in normal language and it fetches real Worklittle data.

Choose MCP when you use an AI assistant and want it working from real job data instead of guessing.

Side by side

| | REST | MCP |
| --- | --- | --- |
| Who sets it up | A developer | Often you, in your AI tool's settings |
| Who uses it | Your software | Your AI assistant |
| Needs code | Yes | Usually no |
| Needs an API key | Yes | Usually yes |

Learn more

- MCP guide for setup instructions - REST vs MCP for the deeper comparison - When to use the API vs the apps if you are not sure you need either