Signal MCP
Provides live integrations with GitHub, Spotify, and blog RSS feeds to power a dynamic portfolio.
README
Signal MCP
Static portfolios are boring.
The Model Context Protocol (MCP) server powers Signal’s live integrations. It connects the system to GitHub activity, Spotify listening history, and blog content, providing real-time data that makes the portfolio feel alive.
What it does
The MCP server is a lightweight Express service that:
- Handles GitHub activity integration
- Connects to Spotify for “Now Playing” and recent history
- Converts blog RSS feeds into consumable JSON
- Exposes MCP-compliant endpoints so the backend can call tools through OpenRouter
It doesn’t interact with models directly. Instead, it responds when the backend orchestrates a tool call, returning structured data that can be streamed back into the conversation.
Architecture overview
The MCP server acts as Signal’s live data provider, bridging the system to external APIs.
Tech stack
- Runtime: Node.js
- Framework: Express
- Protocol: Model Context Protocol (MCP) SDK
- Integrations: GitHub REST API, Spotify Web API, Blog RSS feed
- Dev tooling: ESLint, Prettier, Husky, and shared configs via dev-config
Local development
Signal’s services can be run locally, but setup involves multiple moving parts.
For now, the easiest way to explore Signal is the live demo.
Future work may include a simplified docker-compose flow for local development.
Explore
Signal context
The MCP server reflects how I approach integration boundaries and system interoperability. By isolating third-party APIs behind a single protocol-compliant service, the architecture stays modular and secure. This design makes it easier for teams to extend or swap integrations without affecting the rest of the system. This is a principle I carry into larger engineering projects.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.