Read your DEJAN App data from AI assistants and scripts

AI visibility numbers are most useful where the rest of the work happens: in an AI assistant you use to draft a client update, in a ticketing system that tracks content changes, or in a script that compiles a weekly summary. Getting the numbers there means opening the app, finding the right tab, exporting a CSV and pasting it in, and repeating that every time the numbers change.

Here is an example from our public demo project. Algoroo tracks Google rank volatility. Its Dashboard for 26 October 2026 shows a share of voice of 1.22% across the tracked answers, down 0.02 percentage points over 7 days, and Algoroo 11th of 252 brands mentioned. To put those figures in a weekly email, someone has to read them off the screen.

The DEJAN App runs a server at https://mcp.dejan.ai/mcp that speaks the Model Context Protocol (MCP), the standard AI assistants use to call outside tools. Once you connect a client, it can call DEJAN App tools by name and get the same numbers the app shows. Each tool checks your project membership, so a client sees only the projects you can see in the browser.

Asked for the demo project's visibility, the Get Visibility tool returns the Dashboard headline for the latest day, with the 7-day change for each figure and the top 10 brands.

The server has 17 tools. Sixteen are read-only: they read your data and change nothing. The seventeenth, Start Optimizer Run, starts a Content Optimizer run that tests up to 5 of your own ideas for a query and a page. It spends the project's credits like a run started in the app, and only project owners and editors can use it.

The Content Optimizer tools connect app results to other systems. List Optimizer Runs returns finished runs with baseline and best rank; in the demo project the most recent Algoroo run, on 15 October 2026 for "Algorithm Change Tracking", went from rank 5 to rank 1 with 3 accepted changes. Get Optimizer Recommendations returns each accepted change for a run with its rank factor, the rank before and after, and the old and new text, ready to copy into a ticket.

1. Add the connector URL. In your MCP client, add a custom connector with the URL https://mcp.dejan.ai/mcp. In Anthropic's desktop app this is Settings, then Connectors, then Add custom connector.
2. Sign in with Google. The client opens a sign-in page. Use the Google account you use for the DEJAN App.
3. Click Allow. The authorization page names the client and the account you are signing in as. Allow issues a token for that client; Deny issues nothing.
4. Ask about your projects. Start with List Properties to get project IDs, then ask for a project's visibility, citations or recent runs.
5. Check MCP Connections. Open app.dejan.ai/mcp while signed in. There is no header link; open the address directly. Each connected client is listed with Client, Connected, Last used and Expires.
6. Revoke when done. Revoke invalidates the token at once, so the next call from that client fails. To reconnect, repeat the sign-in from the client, which adds a new row.

• Draft client updates in your assistant. Ask for Get Visibility and Get Top Citations for a project and have the assistant write the weekly summary from the returned figures.
• Sync optimizer results into tickets. Call List Optimizer Runs with the date of your last sync to get only new runs, then Get Optimizer Recommendations for each run to create one ticket per accepted change.
• Test your own ideas from the assistant. Start Optimizer Run takes up to 5 ideas worded your way and tests each one as its own hypothesis. Poll Get Optimizer Recommendations until the run finishes.
• Watch spend from scripts. Get Run Cost and Get Credit Balance return the same figures as the app's cost screens.
• Give each client its own connection. Every authorization is a separate row on MCP Connections, so revoking one device or app leaves the others working. Tokens expire after 90 days.

Open the demo project's Dashboard to see the figures that Get Visibility returns.