Troubleshooting

When a tool call fails.

Your AI assistant passes on the error it got, sometimes in its own words. Find it below, with the fix. First the errors on every tool, then the ones each tool gives itself.

Every tool

Errors from MCP Hosted itself, whichever tool you connect.

The server needs an active subscription
Each tool has its own subscription. Start it on the setup page of the tool, under Connections, and ask again.
No account is connected
Connect your account on the setup page of the tool, under Connections, and ask again.
The connection behind this URL was disconnected
The URL in your assistant belongs to a connection that is gone. Copy the URL of another connection from the setup page and put it in your assistant instead. The URL without a number at the end only reaches the first connection you made, and never moves to another one.
Your tool refuses the key
The key was revoked or expired in the tool itself, or lost a permission. Make a new one and replace the old one on the setup page. The URL stays the same.
Your assistant asks you to sign in again
Its login was switched off under Settings, AI clients, or it ran out. Sign in again from your assistant and approve it. Your other assistants keep working.
Your assistant does not show the tools
Check that the URL is the one on the setup page. Then reconnect the server in your assistant, or restart it: most assistants only load the tools when they connect. Some also let you switch tools off per chat, so check that they are on.
Too Many Attempts (HTTP 429)
Each account can make 60 requests a minute, across all its tools and assistants. Wait a minute and ask again, or ask for fewer things at once.

WeFact

Errors from WeFact itself.

WeFact says there is no access to the API
WeFact only answers addresses on its whitelist. Add our IP address 46.101.201.38, in WeFact under Instellingen and then API. Running the server on your own machine? Add the public IP address of that machine instead.

Laravel Forge

Errors from Laravel Forge itself.

Forge says Invalid scope(s) provided
Your API token lacks the scope the tool needs, often on purpose, to keep your AI read-only. Forge cannot add a scope to a token, so create a new token with that scope and replace the old one on the setup page. Below is the scope of each tool.

The scope each tool needs

list_organizations
organization:view
list_servers
server:view
get_server
server:view
list_sites
server:view
get_site
server:view
create_site
site:create
update_site
site:create
update_site_repository
site:manage-project
list_site_domains
site:meta
create_certificate
site:manage-ssl
set_environment_variables
server:viewsite:manage-environment
get_deployment_script
server:view
update_deployment_script
site:manage-deploys
deploy_site
site:manage-deploys
list_deployments
server:view
get_deployment
server:view
get_deployment_log
site:manage-deploys
reset_deployment_status
site:manage-deploys
run_site_command
site:manage-commands
get_command_output
server:view
create_database
server:create-databases
create_database_user
server:create-databases
create_background_process
server:create-daemons
update_background_process
server:create-daemons
enable_octane
server:create-daemons
enable_inertia_ssr
server:create-daemons
enable_scheduler
server:create-schedulers

Zenvoices

Errors from Zenvoices itself.

Zenvoices refuses the login
Check the organisation code, and the email address and password of the API user. Two-factor authentication and Wachtwoord wijzigen bij volgende login must be off for that user, because the server logs in on its own.
Zenvoices says Required permissions are not granted
Open Rechten for the API user in Zenvoices and tick API, or at least Administraties, Boekingen, Relaties and Uploaden & inlezen under it.

Google Search Console

Errors from Google Search Console itself.

Google no longer accepts this connection
The access was revoked in your Google account, or it expired. Click Reconnect on the setup page and sign in with Google again. The URL stays the same.
The connection is read-only, so it cannot make changes
Click Reconnect on the setup page, pick Read and write and sign in with Google again. The URL stays the same.
A site is missing
The setup page shows the sites each connection can read. Sign in with a Google account that has access to the property in Search Console.

e-Boekhouden

Errors from e-Boekhouden itself.

e-Boekhouden says Login failed
The token is wrong or was deleted. Make a new one under e-Boekhouden API, not API/SOAP (oud), and replace the old one on the setup page. Do not keep trying the old one: e-Boekhouden blocks a token after failed logins.
e-Boekhouden says Access token has expired (API_SESSION_004)
The token is past its Einddatum. Make a new one, leave Einddatum empty and replace the old one on the setup page.

Rompslomp

Errors from Rompslomp itself.

Rompslomp refuses every call
Rompslomp only opens its API on Puur Factuur or a higher plan, so an administration on the free Gratis plan cannot be read. It also refuses when the owner of the API token no longer has access to the administration. Upgrade the plan, or make the token with an account that has access and replace the old one on the setup page.
Rompslomp says the token lacks a scope
Create a new API token in Rompslomp, under Mijn account and then Mijn API tokens, with every scope below ticked, and replace the old one on the setup page.

The scope each tool needs

list_companies
public
list_contacts
manage:contacts
get_contact
manage:contacts
list_sales_invoices
manage:sales_invoices
get_sales_invoice
manage:sales_invoices
list_payments
manage:payments
list_quotations
manage:quotations
list_expenses
manage:expenses
list_accounts
read:accounts

Running it yourself

Errors from the server you run on your own machine with npx.

The tools do not show up
The server did not start. Run the npx command from the setup page in a terminal, with the same environment variables: it prints why, such as a missing or refused license key.
No key is set
Set the environment variables the setup page names in the env of your MCP client config, and restart the client.
No license key found
Set MCPHOSTED_LICENSE_KEY in the env of your MCP client config, next to the key of your tool. Your license key is on the setup page of the tool.
This license covers builds made until (date), and this one is newer
A license covers the builds of one year. Put the version the message names in place of mcphosted in your MCP client config, or buy a new license on the setup page.

Still stuck?

Report it and we will look into it. When a tool fails, the error your assistant gets ends with a link to the form, with the error already filled in.

Report a problem