Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"threads": {
"args": [
"run",
"--project",
"/path/to/ThreadsMcpNet",
"--",
"--mcp"
],
"command": "dotnet"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A .NET 8 MCP (Model Context Protocol) server for publishing content to Threads via the Threads API.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in communication
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
An MCP server that securely interfaces with your iMessage database via the Model Context Protocol (MCP), allowing LLMs to query and analyze iMessage conversations. It includes robust phone number validation, attachment processing, contact management, group chat handling, and full support for sending and receiving messages.
Email & SMS infrastructure for AI agents — send and receive real email and text messages programmatically
A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
MCP Security Weekly
Get CVE alerts and security updates for ThreadsMcpServer and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A .NET 8 MCP (Model Context Protocol) server for publishing content to Threads via the Threads API.
.env.example to .env:cp .env.example .env
.env file with your credentials:HOST=https://graph.threads.net/
APP_ID=your_threads_app_id
APP_SECRET=your_threads_app_secret
REDIRECT_URI=your_redirect_url
Redis__Host=your_redis_host
Redis__User=your_redis_user
Redis__Password=your_redis_password
Redis__Database=0
dotnet restore
dotnet build
For use with Claude Desktop or other MCP clients:
dotnet run -- --mcp
Add to your Claude Desktop configuration (claude_desktop_config.json):
{
"mcpServers": {
"threads": {
"command": "dotnet",
"args": ["run", "--project", "/path/to/ThreadsMcpNet", "--", "--mcp"]
}
}
}
dotnet run
The server will start on port 8080 (or the port specified by the PORT environment variable).
When running as an MCP server, the following tools are exposed:
LoginToThreadsInitiates OAuth login to Threads. Opens the authentication URL in the user's default browser. Must be completed before publishing posts.
CreateAndPublishPostCreates and publishes a text post to Threads.
Parameters:
content (string): The content of the post to publishWhen running in HTTP mode, the following endpoints are available:
GET /init - Server status pageGET /login - Initiate OAuth loginGET /callback - OAuth callback handlerGET /api/me - Get current user infoPOST /api/post - Create and publish a post (query param: input)/mcp - MCP protocol endpointProgram.cs - Main application entry point and configurationAuthService.cs - OAuth authentication logicApiService.cs - Threads API integrationRedisCache.cs - Redis caching implementationFileCache.cs - File-based caching fallbackThe project is configured for Google Cloud Run deployment. See buid-push.sh for build and deployment scripts.
MIT