MCP Server Scaffold
Integrates with Amazon Q CLI, allowing users to access and use tools from the MCP server through Amazon Q, with the tools being available under the 'mcp-server-scaffold___tool-name' namespace.
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., "@MCP Server Scaffold echo back 'Hello, world!'"
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 Server Scaffold
A basic scaffolding project for building Model Context Protocol (MCP) servers.
What is MCP?
The Model Context Protocol (MCP) is an open protocol that standardizes how applications provide context to Large Language Models (LLMs). MCP enables secure, controlled interactions between AI systems and various data sources and tools.
Related MCP server: MCP Template
Features
This scaffold provides:
✅ Basic MCP server implementation
✅ Sample tools (echo, get_current_time)
✅ TypeScript support with proper types
✅ Error handling and logging
✅ Standard MCP protocol compliance
✅ Development and build scripts
Setup
Install dependencies:
npm installBuild the project:
npm run buildStart the server:
npm start
Development
For development with auto-rebuild and restart:
npm run devAvailable Tools
echo
Echoes back the provided message.
Parameters:
message(string, required): The message to echo back
get_current_time
Returns the current date and time in ISO format.
Parameters: None
Project Structure
mcp-server-scaffold/
├── src/
│ └── index.ts # Main server implementation
├── dist/ # Compiled JavaScript (generated)
├── package.json # Project configuration
├── tsconfig.json # TypeScript configuration
└── README.md # This fileExtending the Server
To add new tools:
Add the tool definition in the
ListToolsRequestSchemahandlerAdd the tool implementation in the
CallToolRequestSchemahandlerRebuild and test
Example tool addition:
// In ListToolsRequestSchema handler
{
name: 'my_new_tool',
description: 'Description of what the tool does',
inputSchema: {
type: 'object',
properties: {
param1: {
type: 'string',
description: 'Description of parameter',
},
},
required: ['param1'],
},
}
// In CallToolRequestSchema handler
case 'my_new_tool':
// Your tool implementation here
return {
content: [
{
type: 'text',
text: `Result: ${args.param1}`,
},
],
};Integration with Q CLI
To use this MCP server with Amazon Q CLI:
Build and ensure the server runs correctly
Configure the server in your Q CLI MCP settings
The tools will be available as
mcp-server-scaffold___tool-name
Error Handling
The server includes comprehensive error handling:
Tool execution errors are caught and returned as error responses
Server errors are logged to stderr
Graceful shutdown on SIGINT
License
MIT License - feel free to use this scaffold as a starting point for your own MCP servers.
Available Tools
2 toolsechoB
Echo back the provided message
Inputs: message (required).
get_current_timeB
Get the current date and time
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: 'echo' handles message repetition while 'get_current_time' provides temporal information. There is no overlap in functionality, making it impossible to confuse them.
The naming is mixed: 'echo' uses a simple verb form while 'get_current_time' follows a verb_noun pattern. Although both are readable, they lack a consistent convention, which could lead to unpredictability if more tools were added.
With only 2 tools, this server feels thin for a 'scaffold' purpose, which typically implies a foundation for building more functionality. The count is too low to demonstrate meaningful coherence or coverage for most domains.
Given the vague 'scaffold' domain, it's hard to assess completeness, but the tools cover basic utility operations (echo and time). However, there are obvious gaps for a scaffold, such as file manipulation or configuration tools, limiting its usefulness as a foundation.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Related MCP Servers
- AlicenseDqualityDmaintenanceA ready-to-use starter implementation of the Model Context Protocol (MCP) server that enables applications to provide standardized context for LLMs with sample resources, tools, and prompts.21MIT
- AlicenseBqualityDmaintenanceA template repository for building Model Context Protocol (MCP) servers that enable LLM clients to interact with custom tools and services through standardized JSON-RPC communication.3MIT
- AlicenseNot gradedqualityDmaintenanceA starter project designed to quickly build and deploy Model Context Protocol (MCP) servers using the TypeScript SDK and Zod for schema validation. It features example implementations for tools and resources, providing a solid foundation for custom MCP development and integration.ISC
- AlicenseNot gradedqualityDmaintenanceA starter project designed to help developers quickly build and deploy Model Context Protocol servers using TypeScript and the official SDK. It includes example implementations of tools and resources, such as a calculator and greeting function, to provide a functional foundation for custom MCP development.ISC