# AI Coding Assistants > Connect GitHub Copilot, Cursor, Claude Code and other assistants to the Text Control MCP Server, and install Agent Skills for TX Text Control tasks. - **Product:** TX Text Control .NET Server - **Section:** Documentation - **Kind:** Topic - **Path:** TX Text Control .NET Server > AI Integration > AI Coding Assistants - **3154 words** - **Web URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/ai/coding-assistants/ - **LLMs URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/ai/coding-assistants/llms.txt - **LLMs-Full URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/ai/coding-assistants/llms-full.txt --- GitHub Copilot, Cursor, Claude Code and similar assistants write code from what they know and what they can look up. For TX Text Control, Text Control gives them two sources: the Text Control MCP Server answers their questions from the current documentation, blog and product pages, and Agent Skills give them step-by-step workflows for common tasks. With both in place, a request such as "create a Document Editor application" doesn't need a long prompt that explains the API first. Both tools help you write your application; they don't run inside it. Adding language models to the application itself is the subject of [Agent Workflows](https://docs.textcontrol.com/tx-text-control-dotnet-server/ai/agent-workflows/llms-full.txt) and the other pages of AI Integration. ### Two Tools for Coding Assistants | | Text Control MCP Server | Agent Skills | |---|---|---| | Gives the assistant | Current content: API documentation, blog articles, product features and more | Implementation workflows with verified code for specific tasks | | Installed as | One URL in the MCP configuration of the assistant | Skill folders copied into your workspace | | Kept up to date by | Text Control; the server reads the content of the website | You, by copying newer versions of the folders | | Covers | The whole website, for all products | The Document Editor and `ServerTextControl` | The Text Control MCP Server is a different product from the [MCP Document Server](https://docs.textcontrol.com/tx-text-control-dotnet-server/ai/mcp-server/llms-full.txt), which you host yourself and which creates and edits documents. ### The Text Control MCP Server The Text Control MCP Server is a public, read-only endpoint at `https://www.textcontrol.com/mcp/v1`. It needs no authentication, returns only content that is already public on the Text Control website and can't change any data. It uses the same data as the website, so new blog articles or documentation changes are available immediately. The server implements the MCP specification of 2025-03-26 with the Streamable HTTP transport: a client posts JSON-RPC 2.0 requests to the endpoint and receives JSON. Four methods cover the whole exchange: | Method | Purpose | |---|---| | `initialize` | Exchanges the protocol version and the capabilities of the server | | `ping` | Checks that the server is reachable | | `tools/list` | Returns the 30 tools with the JSON schemas of their parameters | | `tools/call` | Runs a tool with the given arguments | The tools are grouped into eight domains, each with search, list and get operations: | Domain | Tools | Content | |---|---|---| | Documentation | `documentation_search`, `documentation_get`, `documentation_list` | The API documentation pages, filtered by product | | Blog | `blog_search_posts`, `blog_get_post`, `blog_list_posts`, `blog_list_posts_by_tag`, `blog_list_posts_by_author`, `blog_list_tags`, `blog_get_tag`, `blog_get_author`, `blog_list_authors` | Blog articles, tags and authors | | Web search | `web_search`, `web_list`, `web_get` | The pages of the website, searched by title, summary and content and filtered by section: blog, documentation or samples | | Features | `feature_search`, `feature_get`, `feature_list` | Product features | | Pricing | `pricing_search`, `pricing_get`, `pricing_list` | Products with prices in EUR and USD | | Newsletters | `newsletter_search`, `newsletter_list`, `newsletter_get` | Newsletter issues | | Conferences | `conference_search`, `conference_get`, `conference_list` | Conferences where Text Control presented | | Careers | `career_search`, `career_get`, `career_list` | Open positions | Search and list tools return up to 15 results by default and at most 25. Ask for a number of results to set their `limit`; larger result sets are paged with `offset`. When you ask for the full content, the get tools include the complete body as Markdown. ### Connect Your Assistant Add the endpoint to the MCP configuration of your assistant. In Visual Studio Code with GitHub Copilot, add it to *.vscode/mcp.json* in your workspace, or to the user configuration that the **MCP: Open User Configuration** command opens: ```json { "servers": { "textcontrol": { "type": "http", "url": "https://www.textcontrol.com/mcp/v1" } } } ``` Claude Code reads the same entry from *.mcp.json* in your project, or from *~/.claude.json* for all projects, under `mcpServers`: ```json { "mcpServers": { "textcontrol": { "type": "http", "url": "https://www.textcontrol.com/mcp/v1" } } } ``` Other assistants use their own files and keys: | Assistant | Where the endpoint goes | |---|---| | Cursor | *.cursor/mcp.json* in the project, as `url` of an entry under `mcpServers` | | Codex CLI | *~/.codex/config.toml*, as `url` in a `[mcp_servers.textcontrol]` table | | Windsurf | *~/.codeium/windsurf/mcp\_config.json*, as `serverUrl` of an entry under `mcpServers` | | Zed | *~/.config/zed/settings.json*, as `url` of an entry under `context_servers` | | Cline | *cline\_mcp\_settings.json*, as `url` with the type `streamableHttp`, or in the **MCP Servers** view of the Cline panel | | Amazon Q Developer CLI | *~/.aws/amazonq/mcp.json*, as `url` with the type `http` under `mcpServers` | | Claude Desktop | **Settings** > **Connectors** > **Add custom connector**, or *claude\_desktop\_config.json* with the `mcp-remote` bridge started by `npx` | | JetBrains IDEs | **Settings** > **Tools** > **AI Assistant** > **Model Context Protocol** | For other scopes and further settings, see the documentation of your assistant. ### Ask About TX Text Control Once connected, ask in natural language; the assistant chooses the tools: | You ask | The assistant calls | |---|---| | "Search the TX Text Control .NET Server documentation for MailMerge." | `documentation_search` with the query `MailMerge` | | "Which properties does the ServerTextControl class have?" | `documentation_search` to find the class, then `documentation_get` with the full content | | "Find the five most relevant blog posts about mail merge." | `blog_search_posts` with the query `mail merge` and a limit of 5 | | "Find pages about digital signatures in the .NET Server documentation." | `web_search` with the query `digital signatures`, the scope `documentation` and the product `tx-text-control-dotnet-server` | The documentation tools filter by product with `product_name_id`. For this product, the ID is `tx-text-control-dotnet-server`. ### Agent Skills Agent Skills are an emerging open standard for extending AI agents with reusable workflows and domain knowledge. A skill is a folder with a *SKILL.md* file and, usually, a *references* folder: - ***SKILL.md*** starts with front matter that names the skill and describes when to use it. The body lists what the skill can do, example requests with the matching reference file, the workflow the assistant follows and its rules. - ***references*** holds one file per task, with the goal, the source article, the prerequisites, the code and notes. The front matter of the mail merge skill starts like this: ```yaml --- name: txtextcontrol-servertextcontrol-mailmerge description: | Use this skill when a user asks how to build ServerTextControl-based MailMerge workflows with TX Text Control .NET Server. Trigger it for requests involving JSON data merges, XML data merges, object and list merges, merge blocks, skipping rows during merge, and exporting merged output to PDF. metadata: author: Text Control ``` The assistant scans the skills in your workspace, loads the one whose description matches a request and follows its workflow. The rules of the Text Control skills tell it to use only the TX Text Control APIs of the reference files, not to invent APIs, credentials or license keys and not to hardcode license keys. #### The Text Control Skills | Repository | Skill | Use it for | |---|---|---| | [txtextcontrol-document-editor-skills](https://github.com/TextControl/txtextcontrol-document-editor-skills) | `txtextcontrol-aspnetcore-document-editor` | An ASP.NET Core MVC host for the Document Editor, with the private NuGet feed, spell checking and a custom backstage view | | | `txtextcontrol-angular-document-editor` | A Document Editor host with Angular CLI 19 | | | `txtextcontrol-react-document-editor` | A Document Editor host with React | | | `txtextcontrol-document-editor-api` | The JavaScript API: comments, application fields, editable regions, form fields, subtext parts, footnotes, headers and footers, images, tables and tracked changes | | [txtextcontrol-servertextcontrol-skills](https://github.com/TextControl/txtextcontrol-servertextcontrol-skills) | `txtextcontrol-servertextcontrol-mailmerge` | Mail merge with JSON data, objects and lists, merge events, form fields and PDF output | | | `txtextcontrol-servertextcontrol-tables` | Creating and formatting tables, filling them from JSON or CSV and removing empty columns after a merge | | | `txtextcontrol-servertextcontrol-images` | Inserting, positioning, exporting and extracting images; image placeholders in a merge | | | `txtextcontrol-servertextcontrol-headerfooter` | Headers and footers per section, page numbers, first and even pages | | | `txtextcontrol-servertextcontrol-lists` | Bulleted and numbered lists, levels and restarted numbering | | | `txtextcontrol-servertextcontrol-applicationfields` | Inserting, updating, removing and renaming merge fields | | | `txtextcontrol-servertextcontrol-subtextparts` | Named regions, their metadata and conditional merge blocks | | | `txtextcontrol-servertextcontrol-trackchanges` | Filtering, accepting and rejecting tracked changes | | | `txtextcontrol-servertextcontrol-pdfsigning` | Signing PDF and PDF/A documents and signature fields with certificates | For the Document Editor, start with the setup skill of your platform and then use the API skill. The reference files of the `ServerTextControl` skills are based on validated code from the Text Control blog and documentation. #### Install the Skills 1. **Clone the repository**, or download it as a ZIP file: ```bash git clone https://github.com/TextControl/txtextcontrol-servertextcontrol-skills ``` 2. **Copy the skill folders you need** into a folder that your assistant scans: *.github/skills*, *.claude/skills* or *.codestudio/skills* in your workspace: ```text your-workspace/ ├── .github/skills/ │ ├── txtextcontrol-servertextcontrol-mailmerge/ │ │ ├── SKILL.md │ │ └── references/ │ └── txtextcontrol-servertextcontrol-tables/ │ ├── SKILL.md │ └── references/ └── your-project-files... ``` 3. **Start a new chat session**, so that the assistant discovers the skills. #### Use a Skill Describe the task, for example "Create a simple ServerTextControl MailMerge application using a DOCX template and JSON data." The assistant loads the matching skill by itself. When your assistant supports slash commands for skills, you can also name the skill: ```text /txtextcontrol-servertextcontrol-mailmerge create a JSON template merge flow ``` ### Use Both Together The MCP server and the skills complement each other. Asked to create a Document Editor application, an assistant with both loads the setup skill for the steps and queries the MCP server for current API documentation and samples to fill in the details. The blog article [AI Tools: MCP Server and Agent Skills](https://www.textcontrol.com/blog/2026/04/09/text-control-ai-tools-mcp-server-and-agent-skills/) describes this combination. Review the generated code as you would any other code, and build and test it against the version of TX Text Control you use. ### Next Steps - [Document Editor with ASP.NET Core](https://docs.textcontrol.com/tx-text-control-dotnet-server/getting-started/document-editor/aspnet-core/llms-full.txt): set up the Document Editor step by step yourself. - [MCP Document Server](https://docs.textcontrol.com/tx-text-control-dotnet-server/ai/mcp-server/llms-full.txt): host document tools for AI clients in your own application. - [Examples](https://docs.textcontrol.com/tx-text-control-dotnet-server/ai/examples/llms-full.txt): the skill repositories and the other AI samples. --- ## Nearby - **Previous:** [Agent Workflows](https://docs.textcontrol.com/tx-text-control-dotnet-server/ai/agent-workflows/llms-full.txt) - **Next:** [Examples](https://docs.textcontrol.com/tx-text-control-dotnet-server/ai/examples/llms-full.txt)