How do I use MCP Blog Server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP Blog Server show me all blog posts" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

MCP Blog Server

by BunyakornGoko

Overview Schema Source Related Servers Discussions Admin

Python

Remote

MCP Blog Server

A Model Context Protocol (MCP) server that provides blog management tools through a simple API interface. This server allows AI assistants to interact with a blog system to retrieve, search, and create blog posts.

🚀 Features

Get Blogs: Retrieve all available blog posts
Search Blogs: Search for blogs by name/query
Create Blog: Add new blog posts to the system
MCP Integration: Fully compatible with MCP-compatible AI assistants

Related MCP server: blogger-mcp

🛠️ Prerequisites

Python 3.10 or higher
uv package manager (recommended) or pip

📦 Installation

Clone the repository:

git clone <your-repo-url>
cd mcp-by-gokogua

Create a virtual environment:

python3.11 -m venv .venv
source .venv/bin/activate  # On Windows: .venv\Scripts\activate

Install dependencies:
```
uv add "mcp[cli]" httpx
```

🔧 Configuration

Claude Desktop Configuration

To use this MCP server with Claude Desktop, add the following to your claude_desktop_config.json:

{
  "mcpServers": {
    "gokogua-blog": {
      "command": "uv",
      "args": ["--directory", "/path/to/your/project", "run", "main.py"]
    }
  }
}

Note: Replace /path/to/your/project with the actual path to your project directory.

🚀 Usage

Running the Server

# Activate virtual environment
source .venv/bin/activate

# Run the MCP server
uv run main.py

Available Tools

The server provides three main tools:

get_blogs() - Retrieves all blog posts from the API
search_blogs(query: str) - Searches for blogs matching the given query
create_blog(name: str) - Creates a new blog post with the specified name

API Endpoint

The server connects to a mock API at:

https://6898a797ddf05523e55f7ac1.mockapi.io/blogs/Blogs

🏗️ Project Structure

mcp-by-gokogua/
├── main.py              # Main MCP server implementation
├── pyproject.toml       # Project configuration and dependencies
├── README.md            # This documentation
└── .venv/               # Virtual environment (created during setup)

🔌 MCP Integration

This server implements the Model Context Protocol (MCP) using FastMCP, providing a standardized way for AI assistants to interact with external tools and data sources.

Transport

The server uses stdio transport, making it compatible with most MCP clients.

🧪 Testing

To test the server functionality:

Start the server using uv run main.py
Use an MCP-compatible client to connect
Test the available tools through the MCP interface

📝 Dependencies

mcp: Model Context Protocol implementation
httpx: Modern HTTP client for Python
FastMCP: Fast MCP server framework

🤝 Contributing

Fork the repository
Create a feature branch
Make your changes
Submit a pull request

📄 License

This project is open source and available under the MIT License.

🆘 Support

If you encounter any issues:

Check that Python 3.10+ is installed
Verify all dependencies are installed correctly
Ensure the virtual environment is activated
Check the API endpoint is accessible

Available Tools

3 tools

create_blogD

ParametersJSON Schema

Name	Required	Description	Default
`name`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_blogsD

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_blogsD

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

3 tool updatesv0.1.0Jul 13, 2026
- First observedcreate_blog
- First observedget_blogs
- First observedsearch_blogs

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.9/5.0

Scored 2026-07-13 17:06 across 3 tools

Disambiguation5/5

Each tool has a distinct purpose: creating a blog, retrieving all blogs, and searching blogs. No overlap.

Naming Consistency5/5

All tools use consistent verb_noun pattern with underscores.

Tool Count4/5

Three tools is reasonable for a simple blog server, though a bit minimal.

Completeness2/5

Missing update and delete operations, which are essential for full blog management.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

BlogCaster MCP C
io.github.BamaCharanChhandogi
An MCP server for the BlogCaster project.
Content Management Systems Social Media Marketing
72
JustBlogged A
io.github.usamaejaz
Create, edit, organize, publish, and configure JustBlogged blogs from MCP clients.
Content Management Systems Marketing
451
blogbat
io.github.pooriaarab
Hosted MCP for BlogBat: read, write, generate, and publish blog articles and content.
Content Management Systems Marketing Workplace & Productivity
1
Product Management Mcp D
io.github.varvararatta
MCP server for Product Management
Product Management Project Management
2

Related MCP Servers

MCP Blog API
Content Management Systems Developer Tools
tussanakorn
F
license
B
quality
D
maintenance
A simple blog API service built with FastMCP that allows users to fetch all blogs, search for blogs by title, and add new blog posts.
Updated a year ago (2025-05-18 16:12 UTC)
3
-
blogger-mcp
Content Management Systems App Automation
mech12
F
license
A
quality
D
maintenance
A custom MCP server for interacting with Google Blogger blogs. It provides tools to list, create, edit, delete, and publish blog posts through Claude Code or Claude Desktop.
Updated 5 months ago (2026-04-15 02:54 UTC)
9
-
lontar-mcp
Content Management Systems
thesimonharms
F
license
A
quality
F
maintenance
MCP server that gives AI agents full blog management over a Lontar headless blogging API, enabling listing, reading, drafting, publishing, updating, and deleting posts.
Updated 5 days ago (2026-09-09 14:43 UTC)
8
-
MCP_testing
Developer Tools
sharmax-vikas
F
license
Not graded
quality
D
maintenance
Demonstrates a simple MCP client-server setup using fastmcp, with an advanced blog server featuring dynamic resources, tools for post creation and publishing workflows, caching, and async operations.
Updated a year ago (2025-09-10 13:46 UTC)
-

MCP Blog Server

🚀 Features

🛠️ Prerequisites

📦 Installation

🔧 Configuration

Claude Desktop Configuration

🚀 Usage

Running the Server

Available Tools

API Endpoint

🏗️ Project Structure

🔌 MCP Integration

Transport

🧪 Testing

📝 Dependencies

🤝 Contributing

📄 License

🆘 Support

🔗 Related Links

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers