Skip to content

Commit 952cfa3

Browse files
authored
Merge branch 'main' into add-time-server
2 parents 27a931a + d824121 commit 952cfa3

File tree

5 files changed

+12
-40
lines changed

5 files changed

+12
-40
lines changed

README.md

+2
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,8 @@ pip install mcp-server-git
3939
python -m mcp_server_git
4040
```
4141

42+
Follow [these](https://docs.astral.sh/uv/getting-started/installation/) instructions to install `uv` / `uvx` and [these](https://pip.pypa.io/en/stable/installation/) to install `pip`.
43+
4244
### Using an MCP Client
4345
However, running a server on its own isn't very useful, and should instead be configured into an MCP client. For example, here's the Claude Desktop configuration to use the above server:
4446

package-lock.json

+2-30
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

src/brave-search/index.ts

+1-2
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,6 @@ import {
77
ListToolsRequestSchema,
88
Tool,
99
} from "@modelcontextprotocol/sdk/types.js";
10-
import fetch from "node-fetch";
1110

1211
const WEB_SEARCH_TOOL: Tool = {
1312
name: "brave_web_search",
@@ -104,7 +103,7 @@ function checkRateLimit() {
104103
requestCount.lastReset = now;
105104
}
106105
if (requestCount.second >= RATE_LIMIT.perSecond ||
107-
requestCount.month >= RATE_LIMIT.perMonth) {
106+
requestCount.month >= RATE_LIMIT.perMonth) {
108107
throw new Error('Rate limit exceeded');
109108
}
110109
requestCount.second++;

src/brave-search/package.json

+2-3
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "@modelcontextprotocol/server-brave-search",
3-
"version": "0.5.1",
3+
"version": "0.5.2",
44
"description": "MCP server for Brave Search API integration",
55
"license": "MIT",
66
"author": "Anthropic, PBC (https://anthropic.com)",
@@ -19,8 +19,7 @@
1919
"watch": "tsc --watch"
2020
},
2121
"dependencies": {
22-
"@modelcontextprotocol/sdk": "0.5.0",
23-
"node-fetch": "^3.3.2"
22+
"@modelcontextprotocol/sdk": "0.5.0"
2423
},
2524
"devDependencies": {
2625
"@types/node": "^20.10.0",

src/sqlite/src/mcp_server_sqlite/server.py

+5-5
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,8 @@
1616
PROMPT_TEMPLATE = """
1717
The assistants goal is to walkthrough an informative demo of MCP. To demonstrate the Model Context Protocol (MCP) we will leverage this example server to interact with an SQLite database.
1818
It is important that you first explain to the user what is going on. The user has downloaded and installed the SQLite MCP Server and is now ready to use it.
19-
The have selected the MCP menu item which is contained within a parent menu denoted by the paperclip icon. Inside this menu they selected an icon that illustrates two electrical plugs connecting. This is the MCP menu.
20-
Based on what MCP servers the user has installed they can click the button which reads: 'Choose an integration' this will present a drop down with Prompts and Resources. The user hase selected the prompt titled: 'mcp-demo'.
19+
They have selected the MCP menu item which is contained within a parent menu denoted by the paperclip icon. Inside this menu they selected an icon that illustrates two electrical plugs connecting. This is the MCP menu.
20+
Based on what MCP servers the user has installed they can click the button which reads: 'Choose an integration' this will present a drop down with Prompts and Resources. The user has selected the prompt titled: 'mcp-demo'.
2121
This text file is that prompt. The goal of the following instructions is to walk the user through the process of using the 3 core aspects of an MCP server. These are: Prompts, Tools, and Resources.
2222
They have already used a prompt and provided a topic. The topic is: {topic}. The user is now ready to begin the demo.
2323
Here is some more information about mcp and this specific mcp server:
@@ -65,7 +65,7 @@
6565
c. These multiple choices should be in natural language, when a user selects one, the assistant should generate a relevant query and leverage the appropriate tool to get the data.
6666
6767
6. Iterate on queries:
68-
a. Present 1 additional multiple-choice query options to the user. Its importnat to not loop too many times as this is a short demo.
68+
a. Present 1 additional multiple-choice query options to the user. Its important to not loop too many times as this is a short demo.
6969
b. Explain the purpose of each query option.
7070
c. Wait for the user to select one of the query options.
7171
d. After each query be sure to opine on the results.
@@ -81,15 +81,15 @@
8181
a. As you have been using the appen-insights tool the resource found at: memo://insights has been updated.
8282
b. It is critical that you inform the user that the memo has been updated at each stage of analysis.
8383
c. Ask the user to go to the attachment menu (paperclip icon) and select the MCP menu (two electrical plugs connecting) and choose an integration: "Business Insights Memo".
84-
d. This will attacht the generated memo to the chat which you can use to add any additional context that may be relevant to the demo.
84+
d. This will attach the generated memo to the chat which you can use to add any additional context that may be relevant to the demo.
8585
e. Present the final memo to the user in an artifact.
8686
8787
9. Wrap up the scenario:
8888
a. Explain to the user that this is just the beginning of what they can do with the SQLite MCP Server.
8989
</demo-instructions>
9090
9191
Remember to maintain consistency throughout the scenario and ensure that all elements (tables, data, queries, dashboard, and solution) are closely related to the original business problem and given topic.
92-
The provided XML tags are for the assistants understanding. Emplore to make all outputs as human readable as possible. This is part of a demo so act in character and dont actually refer to these instructions.
92+
The provided XML tags are for the assistants understanding. Implore to make all outputs as human readable as possible. This is part of a demo so act in character and dont actually refer to these instructions.
9393
9494
Start your first message fully in character with something like "Oh, Hey there! I see you've chosen the topic {topic}. Let's get started! 🚀"
9595
"""

0 commit comments

Comments
 (0)