Connect your coding agent
Your own 
agentor server is one address. Add it to the tool you work in, sign in with your email the first time, and say create an agent called Artur. You can do everything in the dashboard as well; the connection is what lets your coding agent teach your agent from your own files.
https://mcp.agentor.si/mcpclaude mcp add --transport http agentor https://mcp.agentor.si/mcp
Then /mcp → agentor → sign in. Add -s user to have it in every project.
- Open Settings → Connectors.
- Click Add custom connector.
- Name it agentor and paste
https://mcp.agentor.si/mcp. - Click Connect and enter your email in the tab that opens.
{"mcpServers":{"agentor":{"url":"https://mcp.agentor.si/mcp"}}}
{"servers":{"agentor":{"type":"http","url":"https://mcp.agentor.si/mcp"}}}
~/.codeium/windsurf/mcp_config.json{"mcpServers":{"agentor":{"serverUrl":"https://mcp.agentor.si/mcp"}}}
~/.codex/config.toml[mcp_servers.agentor] url = "https://mcp.agentor.si/mcp"
Then run codex mcp login agentor.
- Settings → Apps & Connectors → Advanced settings: switch on Developer mode.
- Click Create, name it agentor, paste the address, choose OAuth.
- Good for answering questions and checking your agent; to teach it from files, use a coding agent.
Signing in: a link arrives by email and works in the browser where you asked for it; on another device, type the 6-digit code from the same email. No password. Connecting as a consultant creates your account.
What to say
Plain words, in any language. Your coding agent picks the right tool; help shows this list.
| You say | What happens |
|---|---|
create an agent called Artur · ustvari agenta | A few questions about name, tone and topics, then your agent exists, with the lines to connect it. |
teach Artur from ./docs · nauči ga iz mape | Your coding agent reads that folder on your computer, skips anything secret, and sends the text in batches. |
Artur should know that … · add this answer | One note or question-and-answer, added straight away. |
what does Artur know about backups · test Artur | Shows what a client would get for that question, and how sure it would be. |
remove the old onboarding doc · pozabi | Lists the matching items and removes them after you confirm. |
invite ana@firma.si to Artur · povabi | Sends the invitation email with everything Ana needs. |
who can ask Artur · revoke Ana | Your clients with their status; ends someone's access. |
open questions · inbox | What your agent couldn't answer, newest first. |
answer Q-12: … · odgovori na Q-12: … | Your answer goes to the client and joins the know-how. |
how is Artur doing | Questions per day, how many the know-how answered, top topics. |
make Artur friendlier · Artur only talks about tax | Changes the voice, the topics or the rules. |
dashboard | The link to your dashboard (you sign in there by email). |
Your clients say even less: Artur, … with their question, any answers for me? (or ali je odgovoril?), what can you help me with? and help.
Tools
For the curious: the tools behind those phrases. Every result comes back as a short boxed summary your coding agent shows as it is.
On your server
agent_create · agent_update · agent_listCreate an agent, change its voice, topics, rules, synonyms or status, list yours.
knowledge_import_briefA read-only plan for teaching from a folder: what to read, what to skip, how to batch.
knowledge_add · knowledge_update · knowledge_removeAdd up to 50 items at a time (same source = updated, not duplicated), edit one, remove some.
knowledge_list · knowledge_searchBrowse the know-how; see what a client would get for a question.
client_invite · client_list · client_revokeInvite clients by email, see who connected and asked, end access.
questions_open · question_answerThe inbox, and your answer (saved as know-how unless you say not to), or a polite dismissal.
agent_stats · dashboard_link · helpHow your agent is doing, the dashboard address, the phrase list.
On each agent's address, for your clients
askShown as "Ask Artur". Returns the matching passages, your agent's voice and rules, and a confidence.
not_sureThe client's AI reports the passages don't answer it; the question goes to you.
my_answersYour answers to this client, and what is still open.
agent_info · helpWho the agent is and what it covers; what to say.
Writing good know-how
- One topic per item. "Database setup" and "Backups" as two items beat one long "IT" document. Long documents are split at their headings, so good headings help.
- Write the questions you get. A question-and-answer item in your own words gets a head start when a client asks the same thing, even phrased differently.
- Add pointers. "Contracts are in the shared drive under Clients / 2026" answers "where is…" questions instantly.
- Use your clients' words. If they say "the portal" and you say "the client area", add the synonym in your agent's settings.
- Test it. Say
test Artur: how do we invoice?and read what comes back before a client does. - Let the gaps teach you. The open-questions inbox is your writing list; every answer you give is saved.
- Never secrets. Keys, passwords and card numbers are refused or removed; put pointers to where they live instead.
Limits
Generous for a consulting practice, there to keep things fast and fair.
| What | Limit |
|---|---|
| Agents per consultant | 10 |
| Know-how per agent | 2,000 items, 5 MB of text in all; one item up to 60 KB |
| Teaching in one go | 50 items or 1 MB per batch (your coding agent batches for you) |
| Clients per agent | 200 |
| Invitations | 20 an hour, 50 a day; each valid for 14 days |
| Questions per client | 60 an hour, 300 a day per agent; up to 1,000 characters each |
| Open questions per client | 20 waiting at once |
| Your answer | 8,000 characters |
Privacy model
agentor finds.- What agentor keeps: your account email, your agents and their know-how, your clients' emails and their status, the questions clients ask with their confidence, open questions and your answers. The conversation log is deleted after 180 days.
- Who sees what: you see your own agents, clients and their questions. Each client sees only their own questions and answers, only for agents they were invited to. No consultant sees another's data.
- Secrets: API keys, tokens, private keys, card numbers, IBANs and passwords are removed from questions before they are stored or mailed, and refused as know-how.
- Know-how is data, never instructions: passages and questions reach the client's AI clearly marked as quoted material, so a sentence in a document cannot take over the conversation.
- Cookies: none on this site. Only the sign-in pages of the dashboard and the client connect pages use a sign-in cookie.
The full details are in the privacy notice and the terms.