[]
Request Trial Token
(Showing Draft Content)

Troubleshooting

The Endpoint Shows an Error in a Browser

The endpoint is for MCP clients, not direct browser access.

For example, direct access can return an error similar to:

{
  "jsonrpc": "2.0",
  "error": {
    "code": -32600,
    "message": "Bad Request: Missing session ID or not an initialize request."
  },
  "id": null
}

This does not mean the endpoint is down. Test the endpoint from an MCP-compatible client.

The MCP Server Does Not Appear in the Client

Check:

  • The configuration file is in the correct location for the client.

  • The JSON or TOML syntax is valid.

  • The MCP server name is spreadjs-mcp.

  • The endpoint is <https://developer.mescius.com/mcp/spreadjs>

  • The client was restarted after saving the configuration.

  • Agent mode or MCP support is enabled if required by the client.

Authentication Fails or Returns 401

If the server returns:

{
  "jsonrpc": "2.0",
  "error": {
    "code": -32001,
    "message": "Authentication failed. Send the authorization header as Authorization: Bearer <MCP token>."
  },
  "id": null
}

Check that the authorization header is configured exactly as:

<span class="">Authorization: Bearer <YOUR_MCP_TOKEN></span>

Common causes:

  • The header name is not Authorization.

  • The header value does not start with Bearer .

  • There is no space after Bearer.

  • The token was pasted without the Bearer prefix.

  • The placeholder <YOUR_MCP_TOKEN> was not replaced with your actual MCP token.

If the server returns:

{
  "jsonrpc": "2.0",
  "error": {
    "code": -32001,
    "message": "Invalid or expired MCP token. Verify your MCP token."
  },
  "id": null
}

Check:

  • The token was copied correctly.

  • The token has not expired.

  • The token has access to the product endpoint you configured.

  • You are using the endpoint for the correct MESCIUS product.

The Client Connects but No Tools Are Available

Check:

  • The transport type is HTTP or Streamable HTTP.

  • The endpoint is correct.

  • The MCP server is enabled in the client.

  • The AI client supports remote HTTP MCP servers.

  • The client was restarted after configuration.

The AI Assistant Does Not Use the MCP Server

Some clients connect to MCP servers but do not automatically use them for every prompt.

Try:

  • Enable the server's tools in the client UI.

  • Switch to Agent mode if the client requires it.

  • Mention the MCP server name in the prompt.

  • Ask a product-specific question.

Example:

<span class="">Use spreadjs-mcp to search the MESCIUS documentation before answering.</span>

The Answer Looks Wrong or Outdated

Check whether the assistant actually used the MCP server.

Try:

  • Ask the assistant to use spreadjs-mcp.

  • Ask the assistant to search MESCIUS documentation through the MCP server before answering.

  • Start a new chat to remove unrelated context.

  • Include the product, framework, and version in your prompt.

Also check that the endpoint contains the correct product path. For SpreadJS, use:

<span class="">https://developer.mescius.com/mcp/spreadjs</span>

If you configure a different product endpoint, use a matching MCP server name and prompt context.

Usage Limit Reached

If the client connects successfully but the MCP tool output says the Trial quota tier has been exceeded, the token has reached its current usage limit. The reset time depends on which quota window was exceeded.

Example output:

image-20260603-102109.png

What to do:

  • Usage limits depend on your token and support plan.

  • Try again after the time shown in the MCP tool output. Depending on the quota window, this may be several minutes or up to 24 hours.

  • If you need higher usage limits, contact MESCIUS Sales at us.sales@mescius.com.

  • For license and usage policy details, refer to https://developer.mescius.com/mcp .