Connect Moovila Perfect Project
Moovila Perfect Project is project portfolio management for professional-services teams — the projects, phases, tasks, budgets and time entries behind delivery work, plus Moovila's own RPAX risk score…
Written By Christopher Scaminaci
Last updated 6 days ago
Moovila Perfect Project is project portfolio management for professional-services teams — the projects, phases, tasks, budgets and time entries behind delivery work, plus Moovila's own RPAX risk score for each project.
Connecting it gives your AI a set of moovila_ MCP tools — MCP (Model Context Protocol) tools are the standardized commands an AI assistant can call through StackJack. With them, your AI can:
- Report on the portfolio — list projects with their risk scores, forecast dates and due dates, or pull one project in full
- Dig into delivery — tasks with budget-versus-actual and their dependency structure, phases, and project budgets
- Read time and people — time entries with their billing and cost codes, and the user directory
- Resolve the lookup tables — labor types, resource types and products
Read this first: the connector cannot change anything
Moovila's public API is read-only. Every operation it exposes is a read; there is no way to create a project, update a task, or log time through it. That is a property of Moovila's API, not a limitation StackJack chose or a permission you can be granted.
So this connector is genuinely useful for answering questions about your delivery work, and cannot be used to do the work. If you need your AI to create or update Moovila records, that is a conversation to have with Moovila directly — the public API cannot deliver it today.
What it is good at is the thing that is otherwise tedious: pulling risk, schedule and margin signals out of the portfolio and combining them with what StackJack already knows from your PSA and ticketing tools.
What you need
Moovila connects through an App Registration that you create in Moovila, followed by a one-time sign-in. You need:
- Integrations Manager permission in Moovila, to create the App Registration
- A Moovila user account to sign in with when you authorize. The connection reads data with that user's access, so use an account that can see the projects, tasks, time and users you want your AI to report on
- The Redirect URI StackJack shows on the Moovila connector card — it goes into the App Registration as its Callback URL
Create the App Registration in Moovila
- Open Connectors in StackJack, choose Moovila Perfect Project, and copy the Redirect URI shown on the card. Keep this page open.
- In Moovila, click the More Options icon in the left navigation, then Integrations.
- Click the Moovila API tile (it needs Integrations Manager permission), then Add an Application.
- Give the application a name, for example
StackJack. - Paste the Redirect URI from StackJack into the Callback URL field. Moovila lets you save without one, but the sign-in cannot complete without it — the Callback URL is where Moovila sends the authorization back to.
- Under the data elements, tick all four: Projects and Tasks, Users, Time Entries, and Lookup Tables. StackJack asks for all four when you authorize, and Moovila refuses a sign-in whose scopes do not match the registration.
- Click Save. Moovila shows the application's details, including the Client ID and the Client Secret. Copy both.
Connect it in StackJack
- Back on the Moovila connector card, paste the Client ID and the Client Secret.
- Click Authorize. StackJack sends you to Moovila's sign-in page.
- Sign in to Moovila. Moovila sends you back to StackJack, and the connection is stored.
- Use Test Connection. The test reads a small lookup table, so it confirms the connection works without pulling any project data.
Moovila serves one global endpoint, so there is no region to pick and no URL to enter.
StackJack stores the connection encrypted and keeps it current on its own with the refresh token Moovila issues. You do not have to sign in again on a schedule.
If you need to authorize again
You need to authorize again if the sign-in stops being accepted — for example after the App Registration is deleted and recreated, or after its secret is reset in Moovila. Open the Moovila connector card, enter the Client ID and Client Secret again, and click Authorize. The card never shows the stored values, so both fields need to be filled in each time you authorize.
What your AI can do with the data
The endpoint list undersells this connector — the value is in how much each record carries.
Projects come back with Moovila's RPAX score (its risk metric) alongside a forecast date and a due date. That combination is what makes "which projects are at risk?" and "which projects are slipping?" answerable directly, rather than requiring you to export and compare. Projects also flag whether they are templates, so your AI can filter those out — or find them — without a separate call.
Tasks carry budget versus actual (estimated work, total budget, actual and remaining) and dependency flags: whether a task has predecessors, whether it has successors, and whether its predecessors are complete. Moovila's API has no critical-path endpoint, but that dependency information is the raw material, so your AI can reason about what is actually blocking a late task.
Time entries carry billing and cost codes, which makes project profitability questions answerable when combined with the budget data.
Two things to tell your AI
Deleted and inactive records are included. Moovila returns soft-deleted and inactive projects and tasks alongside live ones. If you ask "how many projects do we have?", say "active ones" — otherwise the count will be higher than what you see in Moovila. StackJack's tool descriptions flag this, but it is worth knowing when a number looks wrong.
Ask for changes since a date when you can. Most of the list tools accept a "changed since" filter. For a regular check-in ("what moved this week?"), that is far quicker than re-reading the whole portfolio.
Plans
Moovila's tools are all available on the Free tier because there are no write operations to charge for. Your monthly call allowance still applies as it does for every connector.
Troubleshooting
Test Connection says the connection has not been authorized. The Client ID and Client Secret were saved but the sign-in never completed — this is also the state of a connection set up before the Authorize step existed. Open the connector card, enter the Client ID and Client Secret, and click Authorize.
Moovila's sign-in page says a parameter was not specified, or the scope list is empty. The App Registration's Callback URL does not match the Redirect URI on the StackJack card, or not all four data elements are ticked. Fix the registration in Moovila and click Authorize again.
Test Connection says Moovila no longer accepts the authorization. The refresh token was revoked — usually because the App Registration was deleted or its secret was reset. Authorize again with the current Client ID and Client Secret.
Your AI says it cannot create or update something. That is correct, not a fault. The public API is read-only.
A count looks too high. Deleted and inactive records are included in list results. Ask your AI to exclude them.
Permission errors on some data. The App Registration does not have all four data elements ticked, or the Moovila user who authorized cannot see that data. Tick the missing data elements in Moovila and authorize again.
Full tool list
See the generated Moovila Perfect Project tool reference for the current inventory, plan assignment, input schemas, and destructive-action labels.
Moovila Perfect Project tools
moovila_ · 19 tools · Free 19
Projects
Tasks
Time Entries
Users
Lookup Tables
More in Connector guides
Connect Acronis Cyber Protect CloudConnect Action1Connect AddigyConnect AlertOpsStill need help? Ask the team