# AI Coding Assistants

> Let GitHub Copilot, Claude Code or Cursor search the TX Text Control docs through the MCP Server while you build a WPF app, and learn what Agent Skills cover.

- **Product:** TX Text Control .NET for WPF
- **Section:** Documentation
- **Kind:** Topic
- **Path:** TX Text Control .NET for WPF > Integration Guide > AI Coding Assistants
- **1095 words**
- **Web URL:** https://docs.textcontrol.com/tx-text-control-dotnet-wpf/integration/coding-assistants/
- **LLMs URL:** https://docs.textcontrol.com/tx-text-control-dotnet-wpf/integration/coding-assistants/llms.txt
- **LLMs-Full URL:** https://docs.textcontrol.com/tx-text-control-dotnet-wpf/integration/coding-assistants/llms-full.txt

---

AI coding assistants such as GitHub Copilot, Cursor or Claude Code can look up TX Text Control while they help you write a WPF application. Text Control offers them two sources: the Text Control MCP Server, which answers questions from the documentation, the blog and the product pages, and Agent Skills, which give an assistant step-by-step workflows for specific tasks. What follows shows how to connect an assistant to the MCP server and which skills exist for WPF developers.

Both tools help you write code; neither runs inside your application or needs a package in your project.

### The Text Control MCP Server

The Text Control MCP Server is a public, read-only endpoint of the Model Context Protocol 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. Because it reads the same data as the website, new blog articles and documentation changes reach your assistant as soon as they are published.

The server offers 30 tools in eight areas. For a WPF developer, three of them matter most:

| Area | What the assistant finds there |
|---|---|
| Documentation | The API documentation pages, which are organized by product |
| Blog | The articles of the Text Control Blog, with their tags and authors |
| Web search | All pages of the website, searched by title, summary and content and filtered by section: blog, documentation or samples |

The other areas cover product features, prices, newsletters, conferences and open positions. Because the documentation is available per product, name TX Text Control .NET for WPF in your request, for example "Search the TX Text Control .NET for WPF documentation for the Selection class." The assistant chooses the tools itself.

### 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:

```json
{
  "servers": {
    "textcontrol": {
      "type": "http",
      "url": "https://www.textcontrol.com/mcp/v1"
    }
  }
}
```

Claude Code reads the 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"
    }
  }
}
```

Cursor, JetBrains IDEs, Claude Desktop, Windsurf, Zed, Cline, Amazon Q Developer CLI and Codex CLI connect to the same endpoint with their own configuration files. [Connect Your Assistant](https://docs.textcontrol.com/tx-text-control-dotnet-server/ai/coding-assistants/#connect-your-assistant) in the TX Text Control .NET Server documentation lists the file and the key for each of them, and the 30 tools of the server.

### Agent Skills

A skill is a folder with a *SKILL.md* file, which describes when the skill applies and the workflow the assistant follows, and a *references* folder with the code for each task. You copy the skill folders into a folder of your workspace that your assistant scans, such as *.github/skills* or *.claude/skills*, and start a new chat session. When a request matches the description of a skill, the assistant loads it and follows its workflow.

Text Control publishes two skill repositories:

| Repository | Covers |
|---|---|
| [txtextcontrol-document-editor-skills](https://github.com/TextControl/txtextcontrol-document-editor-skills) | The Document Editor of TX Text Control .NET Server in ASP.NET Core, Angular and React, and its JavaScript API |
| [txtextcontrol-servertextcontrol-skills](https://github.com/TextControl/txtextcontrol-servertextcontrol-skills) | Server-side document processing with `ServerTextControl`: mail merge, tables, images, headers and footers, lists, fields, tracked changes and PDF signing |

Neither repository contains a skill for `WPF.TextControl`, its ribbon or its bars. For a WPF application, the MCP server is the source an assistant can use. [Agent Skills](https://docs.textcontrol.com/tx-text-control-dotnet-server/ai/coding-assistants/#agent-skills) in the TX Text Control .NET Server documentation describes the skills, their installation and their use in detail.

### Licensing and Review

An assistant that works for a licensed developer doesn't need a license of its own, as [Licensing Overview](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/overview/licensing/#developer-licenses) explains. Review the code an assistant writes as you would any other code, and build and test it against the version of TX Text Control your project references.

### Next Steps

- [Create Your First WPF Application](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/getting-started/document-editor/first-application/llms-full.txt): set up the editor step by step yourself.
- [XAML Integration](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/integration/xaml/llms-full.txt): declare the editor and its bars in XAML.
- 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/): how the MCP server and the skills work together.

---

## Nearby

- **Previous:** [Accessibility and UI Automation](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/integration/accessibility/llms-full.txt)
- **Next:** [Deployment Guide](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/deployment/llms-full.txt)