> For the complete documentation index, see [llms.txt](https://docs.launchboard.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.launchboard.org/quick-projects/ai-chats-with-mcp+sqlite.md).

# AI Chats with MCP+SQLite

## Introduction

{% embed url="<https://www.loom.com/share/4d966c291fdd48f181d326ae18102a9d>" %}

**What is this project about?**\
You will be guided on how to quickly offer your own custom abilities to an LLM (Large Language Model) chat, like Claude.ai, without needing to train your own LLM or create a chat interface.  You will do this by creating an MCP server (Model Context Protocol server) that has quickly become an industry standard. You will also be shown how to create and interact with a SQLite database within your MCP server to offer custom data to chat users.

**What tools will we use?**

* Github for managing your server code in a repository
* Python programming in Github Codespaces or similar development environment
* FastMCP Cloud for running your server for public access

Next, take a look at the [quick start with template](/quick-projects/ai-chats-with-mcp+sqlite/quick-start-with-template.md).


---

# 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.launchboard.org/quick-projects/ai-chats-with-mcp+sqlite.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.
