Renesas FSP MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Renesas FSP MCP Server find SPI driver code examples"
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.
π§ Renesas FSP MCP Server
π Overview
FSP (Firmware Support Package) MCP Server is a management and documentation search interface for Renesas Flexible Software Package - the software architecture for Renesas RA MCU family.
This server provides the following capabilities:
π Search documentation from GitHub repository
π» Discover code examples and API references
π¦ Manage dependencies and versions
π οΈ Support development workflow with eΒ² studio
Related MCP server: ABAP MCP Server
β¨ Key Features
1. Documentation Search π
Search FSP documentation from GitHub repository:
Architecture overview
Supported software modules
Driver guides and HAL API references
RTOS integration documentation
Middleware stack documentation
2. Code Examples Discovery π»
Discover code examples for features:
SPI, I2C, UART peripheral drivers
ADC/DAC sampling examples
Secure boot implementation
FreeRTOS integration
DMA-based data transfer
3. API Reference Lookup π
Lookup API documentation:
Core FSP Library (FspLib)
Peripheral drivers (SPI, I2C, UART, etc.)
RTOS integration APIs
Security and cryptographic functions
4. Dependency Management π¦
Manage dependencies and versions:
Version history tracking
Platform compatibility matrix
eΒ² studio version requirements
Minimum hardware specifications
ποΈ System Architecture
βββββββββββββββββββββββββββββββββββββββ
β MCP Server β
β ββββββββββββ¬βββββββββββ¬βββββββββββ β
β β Doc β Examples β API β β
β β Search β Discoveryβ Referenceβ β
β ββββββββββββ΄βββββββββββ΄βββββββββββ β
β β β
β βββββββββββββββββββββββββββββββ β
β β GitHub Repository β β
β β - Documentation β β
β β - Code Examples β β
β β - API References β β
β βββββββββββββββββββββββββββββββ β
βββββββββββββββββββββββββββββββββββββββπ Project Structure
fsp-mcp-server/
βββ src/ # Source code
β βββ index.ts # Main MCP server entry point
β βββ handlers/ # Handler modules
β βββ info.ts # FSP architecture information
β βββ version.ts # Version management
β βββ documentation.ts # Documentation search
β βββ examples.ts # Code examples discovery
β βββ api-reference.ts # API reference lookup
β βββ dependencies.ts # Dependency management
βββ schemas/ # JSON schema definitions
βββ docs/ # Generated documentation
βββ examples/ # Usage examples
βββ package.json # NPM configuration
βββ tsconfig.json # TypeScript configuration
βββ README.md # This fileπ Installation and Usage
1. Install dependencies
cd fsp-mcp-server
npm install2. Build and run
# Build TypeScript code
npm run build
# Run server
npm startOr run directly in development mode:
npm run dev3. Connect to MCP Client
Add the following configuration to your MCP client (e.g., LM Studio, Claude Desktop, etc.):
{
"mcpServers": {
"fsp-mcp-server": {
"command": "node",
"args": ["/path/to/fsp-mcp-server/dist/index.js"]
}
}
}Replace /path/to/fsp-mcp-server with the actual absolute path to your project directory.
For LM Studio:
Open Settings β Extensions β Model Context Protocol.
Add a new MCP endpoint with the command:
node /path/to/fsp-mcp-server/dist/index.js.Set the transport to
stdio.Save and test the connection via MCP Explorer.
π§ Configuration
You can customize the server via package.json:
{
"scripts": {
"build": "tsc && echo 'β
TypeScript compilation complete: dist/index.js'",
"build:clean": "npm run build && find dist -name '*.d.ts' -delete && echo 'π§Ή Cleaned .d.ts files'",
"dev": "tsx watch src/index.ts",
"start": "node ./dist/index.js",
"lint": "eslint \"src/**/*.ts\"",
"format": "prettier --write ."
}
}π References
π License
BSD 3-Clause License - See LICENSE file for details.
π¨βπ» Contributing
To contribute to this project, please:
Fork the repository
Create a branch with your feature (
git checkout -b feature/AmazingFeature)Commit your changes (
git commit -m 'Add some AmazingFeature')Push to the branch (
git push origin feature/AmazingFeature)Open a Pull Request
Available Tools
9 toolsfind_code_examplesC
Find code examples for specific FSP features or peripherals
Inputs: feature, platform.
fsp_build_infoB
Get FSP build-related information
Inputs: no named parameters.
fsp_config_infoC
Get FSP configuration information
Inputs: no named parameters.
fsp_helpB
Get help information for the FSP MCP server
Inputs: no named parameters.
fsp_infoC
Get FSP architecture information and details
Inputs: target.
fsp_versionB
Get FSP version information and release notes
Inputs: no named parameters.
get_api_referenceB
Get API reference documentation for FSP functions and structures
Inputs: module, function.
manage_dependenciesC
Manage FSP dependencies, versions, and compatibility matrix
Inputs: action, platform.
search_documentationC
Search FSP documentation from GitHub repository
Inputs: query, category.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: finding code examples, build info, config info, server help, architecture info, version, API reference, dependency management, and documentation search. No two tools overlap in functionality.
Most tools follow a verb_noun pattern (e.g., find_code_examples, get_api_reference) or use the 'fsp_' prefix (e.g., fsp_config_info). While consistent within groups, mixing these patterns is a minor deviation.
With 9 tools, the server is well-scoped for providing comprehensive FSP information and documentation. Each tool serves a necessary function without redundancy.
The tool set covers the full range of information needs for FSP development: code examples, build/config details, version/architecture, API reference, dependency management, and documentation search. No obvious gaps exist for an informational server.
Maintenance
Related MCP Connectors
Get up-to-date, version-specific documentation and code examples from official sources directly inβ¦
Docsy gives AI assistants current, version-specific documentation for libraries, frameworks and SDKs. Resolve library IDs and versions, then search and fetch focused official documentation with original source links using five read-only MCP tools. Hosted Streamable HTTP with OAuth 2.1 sign-in.
Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.
Versioned documentation registry and semantic search for AI tools and coding assistants.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search documentation of packages and services to find implementation details, examples, and specifications.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceProvides unified ABAP and RAP documentation search, document retrieval, and ABAP feature matrix lookups. It also enables local ABAP linting to streamline development and documentation workflows via the Model Context Protocol.-
- AlicenseNot gradedqualityDmaintenanceEnables CODESYS development assistance via MCP, including curated guidance, Structured Text writing help, local PDF search, and live official documentation lookup.1MIT
- AlicenseAqualityDmaintenanceEnables managing internal documentation with search and add capabilities, and fetching official documentation from 13+ popular libraries via MCP tools.69MIT