Give your agent a reliable Kite reference

Start with public knowledge#

Give your agent access to the University public guide corpus. Use it to understand product terms, prepare a clear brief and find the right help article. Public educational content is separate from your private business memory and current account state.

The University provides read-only search and guide tools. Responses include the guide version, stable section anchors, source titles and checked dates. They cannot start work or read a private Kite workspace.

The University address is https://kitegtm.com/university/api/mcp. Your private Kite connection uses https://api.kitegtm.com/mcp, where you sign in and allow access. Check your client's connected tool list: having the private connection does not establish that University search is available there. Use the separate University connection when needed. If a connection is unavailable, report that limitation and work from the guide or business facts the user supplied.

Retrieve before recommending#

Search for the problem in the user's own words. Retrieve the most relevant guide, read its source information and cite the returned canonical URL with the section anchor you used. Include the guide version when reporting the reference. Internal review and publication records are not part of the public response.

Discover each tool's current schema before calling it. The public University get_university_guide takes the returned guide id; read the section and version from its response. An account connector may expose a different schema. Do not add a version, section, workspace ID or other argument unless that tool accepts it. If the guide changes between search and retrieval, use the retrieved version or search again before giving a version-specific answer.

A missing public guide is not evidence that a feature exists or that an account is ready. Ask for the missing information or direct the user to the relevant product review.

Try the read-only recipe#

The recipe below searches University guidance. Follow it with get_university_guide using a returned ID. Read the result before recommending a step. These calls return knowledge; they grant no authority to execute the steps they describe.

For Codex, add a remote HTTP server with codex mcp add kite-university --url https://kitegtm.com/university/api/mcp. For Claude Code, use claude mcp add --transport http kite-university https://kitegtm.com/university/api/mcp. Check /mcp in your client after connecting. No Kite account sign-in is needed for public University guidance. The private connection's setup and sign-in steps are on the agent access page.

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "search_university",
    "arguments": {
      "query": "start with an objective"
    }
  }
}

Keep preparation and activation clear#

An agent can help shape an objective and required criteria. Use Kite's actual review and start controls to activate a mission. Do not infer permission to send, spend, change settings or enrol people from a request to explain a guide.

For an account task, use only the connected reads needed to answer it. Keep the resulting account facts separate from the public lesson. A guide can explain what a readiness check means; it cannot confirm your sending connection, balance, permissions or mission status. Do not copy public lessons into your private business Memory.

Your next step#

Start with the objective tutorial to prepare a clear brief. Then follow the first-Introduction agent tutorial to read recommendations, prepare a selected setup when requested and return the correct Kite review step.