Frequently asked questions

Does it cost anything?

No. The Learnosity Build Aide MCP server is provided at no cost.

Do I need a Learnosity account or API credentials to connect?

No. The server requires no authentication. You will need credentials to run the integration you build, but not to use the MCP server.

Which AI assistants and IDEs are supported?

Any client supporting the MCP HTTP transport. This includes VS Code, Cursor, Kiro, and Claude Code, among others - all of which have been tested.

How many tools does the server expose?

The Learnosity Build Aide MCP server exposes eight tools. The list_docs_sources, list_docs_categories, search_docs_sources, and read_document tools provide access to documentation. The skills_list, skills_read, and skills_search tools provide access to Skills. The get_feedback_link tool provides a link for sharing feedback.

For more information, see Tools in the Using Learnosity Build Aide MCP article.

What is the difference between tools and resources?

Tools and resources provide access to the same content in different ways. Your AI coding assistant calls tools, while resources are accessed using a learnosity:// URI. Search results include both an article identifier and the corresponding resource URI.

Why did my search return a golden path alert?

A golden path alert can appear when your search query or its results reference a lower-level API. The alert recommends the corresponding API from the Learnosity golden path and can indicate when results for the lower-level API have been withheld.

For more information, see Search and the golden path gate.

Can I turn the golden path gate off?

No. To retrieve results for a lower-level API when the golden path gate withholds them, set off_golden_path_reason to the reason your integration requires that API. Specify the parameter on each applicable search request because the value does not persist between requests.

Can it write code for me?

Your assistant writes the code. The MCP server supplies accurate Learnosity knowledge for it to work from - which is the difference between code that runs and code that looks like it should.

Will it sign my requests?

No, and this is deliberate. Signing requires your secret, and your secret should never leave your environment. The server explains signing thoroughly; your application performs it.

How current is the information?

The documentation index refreshes every 24 hours from the published Learnosity sources, so answers reflect the current documentation.

Which documentation does it cover?

The Learnosity Help site, the Author Guide site, Feedback Aide backend documentation, the Learnosity Demos site, and Learnosity's public GitHub repositories. For more information, see Documentation available through Learnosity Build Aide MCP in the Using Learnosity Build Aide MCP article.

Does it support version-specific (LTS) guidance?

Yes, LTS-aware guidance is supported, and the LTS Upgrade Paths Skill is built around it. Coverage continues to expand as version-aware documentation rolls out.

Is my code or prompt data sent to Learnosity?

Only the tool your assistant calls reaches the server. Learnosity collects anonymised operational metrics - tool name, timing, error type - to monitor service health. Your source code is not transmitted.

What if a Skill I need does not exist yet?

The catalog is driven directly by customer pain points. Tell us what you need - see Provide Feedback.

 

Was this article helpful?

Did you arrive here by accident? If so, learn more about Learnosity.