day 15 #111
Merged
day 15 #111
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds Day 15 documentation to the "First 30 Days with EchoKit" series, focusing on integrating MCP (Model Context Protocol) for web search capabilities. It also includes minor formatting corrections to the Day 14 documentation.
- Introduces MCP integration documentation with configuration examples and use cases
- Corrects separator formatting in Day 14 documentation
- Demonstrates web search tool integration using Groq and Tavily MCP server
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| doc/dev/2025-12-10-echokit-day-15-mcp-web-search.md | New documentation for Day 15 covering MCP integration, explaining the protocol, configuration steps, and practical web search examples |
| doc/dev/2025-12-10-echokit-day-14-personality.md | Formatting fix: removed incorrectly placed separator and added proper markdown separator |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| To make EchoKit call external tools, we simply point it to an MCP server. Add a section like the following to your config.toml: | ||
|
|
||
| ``` |
There was a problem hiding this comment.
Missing language identifier for code block. According to the repository convention, code blocks for configuration examples should include the toml language identifier. Change totoml for proper syntax highlighting.
| To demonstrate, let’s connect EchoKit to a web‑search MCP server. Many open‑source servers provide a search tool that scrapes public search engine results—often without requiring API keys. | ||
|
|
||
| Adding the server to your configuration. Here I use the GPT-OSS-120B model hosted on Groq and the tavily MCP server: | ||
| ``` |
There was a problem hiding this comment.
Missing language identifier for code block. According to the repository convention, code blocks for configuration examples should include the toml language identifier. Change totoml for proper syntax highlighting.
|
|
||
| ## 🧠 What is MCP? | ||
|
|
||
| MCP acts like a “USB‑C port” for AI agents. It defines a client–server protocol that lets models call external tools, databases or APIs through standardised actions. MCP servers wrap services—such as file systems, web searches or device controls—behind simple JSON‑RPC endpoints. MCP Clients (like EchoKit or Anthropic’s Claude Code) connect to one or more MCP servers and dynamically discover available tools. When the model needs information or wants to perform an action, it sends a tool request; the server executes the tool and returns results for the model to use |
There was a problem hiding this comment.
Missing period at the end of the sentence.
Suggested change
| MCP acts like a “USB‑C port” for AI agents. It defines a client–server protocol that lets models call external tools, databases or APIs through standardised actions. MCP servers wrap services—such as file systems, web searches or device controls—behind simple JSON‑RPC endpoints. MCP Clients (like EchoKit or Anthropic’s Claude Code) connect to one or more MCP servers and dynamically discover available tools. When the model needs information or wants to perform an action, it sends a tool request; the server executes the tool and returns results for the model to use | |
| MCP acts like a “USB‑C port” for AI agents. It defines a client–server protocol that lets models call external tools, databases or APIs through standardised actions. MCP servers wrap services—such as file systems, web searches or device controls—behind simple JSON‑RPC endpoints. MCP Clients (like EchoKit or Anthropic’s Claude Code) connect to one or more MCP servers and dynamically discover available tools. When the model needs information or wants to perform an action, it sends a tool request; the server executes the tool and returns results for the model to use. |
|
|
||
| The MCP server performs the web search and returns structured results (titles, URLs and snippets). EchoKit then synthesises a natural‑language answer, summarising the findings and citing the sources. | ||
|
|
||
| You can also use other MCP sever tools like the Google Calendar MCP server to add and edit event, Slack MCP server to send an message to the Slack channel, Home Assistant MCP server to control the home device. All of these tools become accessible through your voice. |
There was a problem hiding this comment.
Multiple spelling and grammar errors: 'sever' should be 'server', 'edit event' should be 'edit events', 'send an message' should be 'send a message', and 'the home device' should be 'home devices'.
Suggested change
| You can also use other MCP sever tools like the Google Calendar MCP server to add and edit event, Slack MCP server to send an message to the Slack channel, Home Assistant MCP server to control the home device. All of these tools become accessible through your voice. | |
| You can also use other MCP server tools like the Google Calendar MCP server to add and edit events, Slack MCP server to send a message to the Slack channel, Home Assistant MCP server to control home devices. All of these tools become accessible through your voice. |
|
|
||
| ## 📌 Why This Matters | ||
|
|
||
| Integrating MCP gives EchoKit access to a rapidly expanding tool ecosystem. You’re no longer limited to predetermined voice commands; your agent can search the web, read files, run code, query databases or control smart devices—all through a the voice interface. The AAIF’s stewardship of MCP ensures that these capabilities remain open and interoperable, so EchoKit can continue to evolve alongside the broader agentic AI community. |
There was a problem hiding this comment.
Extra article: 'a the voice interface' should be 'a voice interface' (remove 'the').
Suggested change
| Integrating MCP gives EchoKit access to a rapidly expanding tool ecosystem. You’re no longer limited to predetermined voice commands; your agent can search the web, read files, run code, query databases or control smart devices—all through a the voice interface. The AAIF’s stewardship of MCP ensures that these capabilities remain open and interoperable, so EchoKit can continue to evolve alongside the broader agentic AI community. | |
| Integrating MCP gives EchoKit access to a rapidly expanding tool ecosystem. You’re no longer limited to predetermined voice commands; your agent can search the web, read files, run code, query databases or control smart devices—all through a voice interface. The AAIF’s stewardship of MCP ensures that these capabilities remain open and interoperable, so EchoKit can continue to evolve alongside the broader agentic AI community. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.