> For the complete documentation index, see [llms.txt](https://docs.superteamde.fun/superteam-germany-guilds/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.superteamde.fun/superteam-germany-guilds/build-on-solana/ai-and-mcp-tools.md).

# AI & MCP Tools

AI-native tools, MCPs, and agent-oriented workflows for Solana builders.

This page is for builders who use AI-native workflows while shipping on Solana.

## Core Links

* [Solana MCP](https://mcp.solana.com/) for the official Solana knowledge and workflow server
* [How to get started with AI tools on Solana](https://solana.com/developers/guides/getstarted/intro-to-ai) for the official overview
* [AI on Solana](https://solana.com/ai) for the broader ecosystem direction
* [Solana Agent Kit](https://docs.sendai.fun/) for transaction-capable agent workflows
* [solana.new](https://www.solana.new/) for fast AI-assisted project setup

## When This Helps Most

* rapid prototyping during hackathons
* scaffolding and exploring project directions
* looking up Solana-specific implementation details inside an IDE
* combining codegen, docs lookup, and transaction-capable agent workflows

## A Practical Stack

1. start from official docs and templates
2. use Solana MCP inside your IDE
3. use `solana.new` or Agent Kit style workflows when they make shipping faster
4. still verify security-critical details against canonical docs before deploying


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.superteamde.fun/superteam-germany-guilds/build-on-solana/ai-and-mcp-tools.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.