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.

REST is for software you build. MCP is for AI assistants.

REST

A program asks Worklittle for data directly. A developer writes code that requests "software jobs in Austin" and gets a structured answer. Use REST for a careers page, dashboard, or a sync into another system.

MCP

MCP plugs Worklittle into an AI assistant so it can look things up itself. Connect it once, then ask in normal language and the assistant fetches real Worklittle data. Use MCP when you want an AI assistant working from real job data instead of guessing.

Comparison

| | 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 |

See the MCP guide, REST vs MCP, and When to use the API vs the apps.