Custom MCPsBuilding custom Model Context Protocol servers that wrap internal APIs so an AI assistant can read and act on the systems I work in directly
View all tags
Have you ever worked with a CMS or CCMS that required lots of repetitive clicking through the UI to get things done? If the tool has a REST API, you can trade those clicks for natural language prompts by building an MCP (Model Context Protocol) server that's a simple API wrapper and use it with an AI agent skill. Here's how I did it using Claude to handle the coding.
This is part of a series about custom MCP servers I've built to connect the systems I work in, so I can generate content from the information they hold, set up workflows that cover multiple tools, and eliminate manual, repetitive work that would otherwise only be possible through the application UI.
This is part of a series about custom MCP servers I've built to connect the systems I work in, so I can generate content from the information they hold, set up workflows that cover multiple tools, and eliminate manual, repetitive work that would otherwise only be possible through the application UI.
This is part of a series about custom MCP servers I've built to connect the systems I work in, so I can generate content from the information they hold, set up workflows that cover multiple tools, and eliminate manual, repetitive work that would otherwise only be possible through the application UI.
This is part of a series about custom MCP servers I've built to connect the systems I work in, so I can generate content from the information they hold, set up workflows that cover multiple tools, and eliminate manual, repetitive work that would otherwise only be possible through the application UI.