Skip to content

Commit c3633d8

Browse files
actions-useractions-user
committed
Update repo with server manifest from issue #104 
1 parent 1945250 commit c3633d8

File tree

1 file changed

+211
-0
lines changed

1 file changed

+211
-0
lines changed

‎mcp-registry/servers/[email protected]‎

Lines changed: 211 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,211 @@
1+
{
2+
"display_name": "Prisma MCP Server",
3+
"license": "Apache 2.0",
4+
"tags": [
5+
"database",
6+
"ORM",
7+
"TypeScript",
8+
"Node.js",
9+
"PostgreSQL",
10+
"Prisma",
11+
"MCP"
12+
],
13+
"installations": {
14+
"npm": {
15+
"type": "npm",
16+
"command": "npx",
17+
"args": [
18+
"-y",
19+
"prisma",
20+
"mcp"
21+
],
22+
"description": "Start the Prisma MCP server"
23+
}
24+
},
25+
"examples": [
26+
{
27+
"title": "",
28+
"description": "",
29+
"prompt": "Create a new Prisma Postgres database instance"
30+
},
31+
{
32+
"title": "",
33+
"description": "",
34+
"prompt": "Generate a Prisma schema for a blog application with User and Post models"
35+
},
36+
{
37+
"title": "",
38+
"description": "",
39+
"prompt": "Run a schema migration on my Prisma Postgres database"
40+
},
41+
{
42+
"title": "",
43+
"description": "",
44+
"prompt": "Help me set up Prisma Client in my Node.js application"
45+
},
46+
{
47+
"title": "",
48+
"description": "",
49+
"prompt": "How do I query all users with their related posts using Prisma Client?"
50+
},
51+
{
52+
"title": "",
53+
"description": "",
54+
"prompt": "Update my database schema to add a Comment model related to Posts"
55+
},
56+
{
57+
"title": "",
58+
"description": "",
59+
"prompt": "Show me how to filter Posts that contain a specific keyword"
60+
}
61+
],
62+
"name": "@prisma/prisma",
63+
"repository": {
64+
"type": "git",
65+
"url": "https://github.com/prisma/prisma"
66+
},
67+
"homepage": "https://github.com/prisma/prisma",
68+
"author": {
69+
"name": "prisma"
70+
},
71+
"description": "Prisma ORM is a **next-generation ORM** that consists of these tools:",
72+
"categories": [
73+
"Dev Tools"
74+
],
75+
"tools": [
76+
{
77+
"name": "migrate-status",
78+
"description": "The prisma migrate status command looks up the migrations in ./prisma/migrations/* folder and the entries in the _prisma_migrations table and compiles information about the state of the migrations in your database.\n Example output:\n\n Status\n 3 migrations found in prisma/migrations\n\n Your local migration history and the migrations table from your database are different:\n\n The last common migration is: 20201127134938_new_migration\n\n The migration have not yet been applied:\n 20201208100950_test_migration\n\n The migrations from the database are not found locally in prisma/migrations:\n 20201208100950_new_migration",
79+
"inputSchema": {
80+
"type": "object",
81+
"properties": {
82+
"projectCWD": {
83+
"type": "string"
84+
}
85+
},
86+
"required": [
87+
"projectCWD"
88+
],
89+
"additionalProperties": false,
90+
"$schema": "http://json-schema.org/draft-07/schema#"
91+
}
92+
},
93+
{
94+
"name": "migrate-dev",
95+
"description": "Prisma Migrate Dev is used to update Prisma whenever the schema.prisma file has been modified. Always provide a descriptive name argument describing the change that was made to the Prisma Schema.\n\n The migrate dev command performs these steps:\n\n 1. Reruns the existing migration history in the shadow database in order to detect schema drift (edited or deleted migration file, or a manual changes to the database schema)\n 2. Applies pending migrations to the shadow database (for example, new migrations created by colleagues)\n 3. Generates a new migration from any changes you made to the Prisma schema before running migrate dev\n 4. Applies all unapplied migrations to the development database and updates the _prisma_migrations table\n 5. Triggers the generation of artifacts (for example, Prisma Client)",
96+
"inputSchema": {
97+
"type": "object",
98+
"properties": {
99+
"name": {
100+
"type": "string"
101+
},
102+
"projectCWD": {
103+
"type": "string"
104+
}
105+
},
106+
"required": [
107+
"name",
108+
"projectCWD"
109+
],
110+
"additionalProperties": false,
111+
"$schema": "http://json-schema.org/draft-07/schema#"
112+
}
113+
},
114+
{
115+
"name": "migrate-reset",
116+
"description": "Prisma Migrate Reset --force is used to reset the database and migration history if drift is detected. Only run this command on a development database - never on production databases! If in doubt, ask the user to confirm.\n\n The migrate reset command performs these steps:\n\n 1. Drops the database/schema if possible, or performs a soft reset if the environment does not allow deleting databases/schemas\n 2. Creates a new database/schema with the same name if the database/schema was dropped\n 3. Applies all migrations\n 4. Runs seed scripts",
117+
"inputSchema": {
118+
"type": "object",
119+
"properties": {
120+
"projectCWD": {
121+
"type": "string"
122+
}
123+
},
124+
"required": [
125+
"projectCWD"
126+
],
127+
"additionalProperties": false,
128+
"$schema": "http://json-schema.org/draft-07/schema#"
129+
}
130+
},
131+
{
132+
"name": "Prisma-Postgres-account-status",
133+
"description": "Prisma Platform Auth Show provides information about the currently logged in user. If the user is not logged in, you should instruct them to do so by running `npx prisma platform auth login --early-access` and then re-running this command to verify.",
134+
"inputSchema": {
135+
"type": "object",
136+
"properties": {
137+
"projectCWD": {
138+
"type": "string"
139+
}
140+
},
141+
"required": [
142+
"projectCWD"
143+
],
144+
"additionalProperties": false,
145+
"$schema": "http://json-schema.org/draft-07/schema#"
146+
}
147+
},
148+
{
149+
"name": "Create-Prisma-Postgres-Database",
150+
"description": "Create a new online Prisma Postgres database.\n Specify a name that makes sense to the user - maybe the name of the project they are working on.\n Specify a region that makes sense for the user. Pick between these three options: us-east-1, eu-west-3, ap-northeast-1. If you are unsure, pick us-east-1.\n Provide the current working directory of the users project. This should be the top level directory of the project.\n If the response idicates that you have reached the workspace plan limit, you should instruct the user to do one of these things:\n - If they want to connect to an existing database, they should go to console.prisma.io and copy the connection string\n - If they want to upgrade their plan, they should go to console.prisma.io and upgrade their plan in order to be able to create more databases\n - If they want to delete a database they no longer need, they should go to console.prisma.io and delete the database project",
151+
"inputSchema": {
152+
"type": "object",
153+
"properties": {
154+
"name": {
155+
"type": "string"
156+
},
157+
"region": {
158+
"type": "string"
159+
},
160+
"projectCWD": {
161+
"type": "string"
162+
}
163+
},
164+
"required": [
165+
"name",
166+
"region",
167+
"projectCWD"
168+
],
169+
"additionalProperties": false,
170+
"$schema": "http://json-schema.org/draft-07/schema#"
171+
}
172+
},
173+
{
174+
"name": "Prisma-Login",
175+
"description": "Login or create an account in order to be able to use Prisma Postgres.",
176+
"inputSchema": {
177+
"type": "object",
178+
"properties": {
179+
"projectCWD": {
180+
"type": "string"
181+
}
182+
},
183+
"required": [
184+
"projectCWD"
185+
],
186+
"additionalProperties": false,
187+
"$schema": "http://json-schema.org/draft-07/schema#"
188+
}
189+
},
190+
{
191+
"name": "Prisma-Studio",
192+
"description": "Open Prisma Studio to view data in your database in a pleasing visual ui.\n Provide the current working directory of the users project. This should be the top level directory of the project.",
193+
"inputSchema": {
194+
"type": "object",
195+
"properties": {
196+
"projectCWD": {
197+
"type": "string"
198+
}
199+
},
200+
"required": [
201+
"projectCWD"
202+
],
203+
"additionalProperties": false,
204+
"$schema": "http://json-schema.org/draft-07/schema#"
205+
}
206+
}
207+
],
208+
"prompts": [],
209+
"resources": [],
210+
"is_official": false
211+
}

0 commit comments

Comments
 (0)