Skip to the page

DocsAI workers

DocsAI workers

Data sources and Atlas-bot

Connect a project to your own MCP server so AI workers such as Atlas-bot can answer tasks from your data, using only the read-only tools you allow.

Business plan and aboveFor owners and admins

A data source connects a project to an MCP server that you run, in front of your own database or warehouse. AI workers you allow can then call the server’s read-only tools while they work on that project’s tasks. Atlas-bot, the starter data worker, is made for this: give it a question as a task and it answers from your data.

Projik never holds your database credentials. It holds the address of your MCP server and a token for it, and you decide which tools exist.

Connect a data source and ask Atlas-bot a question

Video coming soon2:00

In this video: Starts in a project’s settings on Data sources. A name, an MCP server URL and a token are entered and Test and connect lists the server’s tools. Two read-only tools and Atlas-bot are ticked and saved. A task asking for last week’s sign-ups is given to Atlas-bot; its answer arrives as a comment with a short table. On Atlas-bot’s page the run opens to show the queries it made.

Before you start#

  • Use a read-only database role. Projik only lets workers call tools your server marks as read-only, but that label is your server’s promise, not a guarantee. Connect a server that reaches your database with a role that can only read.
  • The server must be reachable from the internet over HTTPS. See the address.
  • The worker must be one Projik runs. Atlas-bot is. See workers Projik runs.

Connect a data source#

  1. Open the project, choose Settings in its header, then Data sources.
  2. Give the connection a Name, such as “Warehouse (read-only)”.
  3. Enter the MCP server URL: the full address, path included.
  4. Enter the Token. It’s sent as Authorization: Bearer …. If your server expects the token in a different header, open Another header and give the Header name, such as X-Api-Key. Leave the token empty if the address carries its own key.
  5. Choose Test and connect.

Projik connects to the server and lists its tools before saving anything. If the server can’t be reached or refuses the token, nothing is saved and the message says why.

A project can have up to five data sources.

The address#

  • It must start with https://.
  • It must be a public address. Local and private network addresses, and names ending in .local or .internal, are refused.
  • It can’t contain a username or password.
  • Projik doesn’t follow redirects. If your server answers with one, give the address it redirects to.
  • The server must speak MCP over HTTP (Streamable HTTP). Projik waits up to 20 seconds for it to connect.

Choose the tools and the workers#

Each connection shows two lists.

Tools AI workers may call. Tick the tools you want to allow. Only tools the server marks read-only can be ticked. A tool that can change data is listed as “Changes data: not available yet” and can’t be allowed.

AI workers who may use it. Tick the workers. Only AI workers who can see the project are listed, and no worker can use the connection until you tick it.

Choose Save.

How a worker uses it#

When an allowed worker works on a task in the project, it’s offered the ticked tools along with the task. It decides which to call, reads the results and writes its answer as a comment on the task, as usual. The task then goes to review.

At the start of each run Projik fetches the server’s tool list afresh, and offers only the ticked tools that are still marked read-only. Before every call it checks again that the connection is still there and that the tool and the worker are still allowed.

Limits#

LimitAmount
Data calls in one run20
Time for one call30 seconds
Rows of one result the worker sees200
Size of one result the worker sees50 KB
Rows of a table in the posted answer20

A result that’s cut carries a note saying so, which tells the worker to ask a narrower question. Results count towards the AI allowance through the text they add to the run.

Where each query is listed#

Open the worker’s page and find the run under Recent runs. A line such as “2 data queries” opens the list: the data source and tool, the arguments it sent (the query text, for example), how many rows came back, whether the result was cut, how long it took, or why it failed.

Projik keeps this record of each call and never stores the results. Anyone who can see the task’s project can see the list.

Keep a connection working#

  • Test again reconnects and refreshes the list of tools. If an allowed tool has gone, or is no longer marked read-only, it’s taken off the allowed list.
  • A connection is marked Connected or Failing, with the last error and when it was last tested.
  • Replace URL or token swaps in a new address or token and tests it before saving.

Remove a connection#

Choose Remove…, then Remove for good. The stored address and token are deleted, and workers can no longer call the server. In an archived project, data sources are read-only but can still be removed.

How your credentials are kept#

The server’s address and token are stored encrypted and are never shown again, to you or anyone else. A saved connection shows only the server’s host name. They’re used only to call your server, and aren’t given to the AI model.

What the worker reads does go to the model that runs it. If the worker runs on your own model key, the results of its queries are sent to that provider.

Plan#

Data sources need the Business plan, and are included in a new workspace’s trial. If the workspace moves to a plan without them, connections are kept but workers aren’t offered their tools.

    Type to search every page. ↑ ↓ to move, Enter to open.