Add Server Instructions content #1334
Draft
+411
−82
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
… and adding a specific example for implementing server instructions
connor4312
reviewed
Aug 12, 2025
docs/clients.mdx
Outdated
| | [TheiaAI/TheiaIDE][TheiaAI/TheiaIDE] | ❌ | ❌ | ✅ | ❓ | ❌ | ❌ | ❓ | ❌ | | ||
| | [Tome][Tome] | ❌ | ❌ | ✅ | ❓ | ❌ | ❌ | ❓ | ❌ | | ||
| | [TypingMind App][TypingMind App] | ❌ | ❌ | ✅ | ❓ | ❌ | ❌ | ❓ | ❌ | | ||
| | [VS Code GitHub Copilot][VS Code] | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | |
There was a problem hiding this comment.
we support it :) microsoft/vscode-copilot-chat#491
Suggested change
| | [VS Code GitHub Copilot][VS Code] | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | | |
| | [VS Code GitHub Copilot][VS Code] | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| - [ ] Add edit/disable capabilities | ||
| - [ ] Log instruction usage | ||
| - [ ] Set reasonable length limits | ||
| - [ ] Sanitize before prompt injection |
There was a problem hiding this comment.
I'm not necessarily sure if server instructions need special treatment here. Prompt injection is also possible and demonstrated using tool descriptions themselves, so as a client developer do instructions need to be treated any different than tools?
|
|
||
| - 'Tool C should always be used after tool A and B' | ||
| - 'This Prompt or Tool works best if specialized tools from other servers X and Y are available' | ||
| - 'All Tools are rate limited to 10 requests per minute' |
There was a problem hiding this comment.
It's up to the client how to present the instructions, but I could see cases where the LM could get confused about the context of "all tools", perhaps we should recommend that instead the statement is something like "Server A tools are rate limited to 10 requests per minute"
Co-authored-by: Den Delimarsky <hi@den.dev>
Co-authored-by: Den Delimarsky <hi@den.dev>
Co-authored-by: Den Delimarsky <hi@den.dev>
Co-authored-by: Den Delimarsky <hi@den.dev>
Co-authored-by: Den Delimarsky <hi@den.dev>
Co-authored-by: Den Delimarsky <hi@den.dev>
Co-authored-by: Den Delimarsky <hi@den.dev>
Co-authored-by: Den Delimarsky <hi@den.dev>
Co-authored-by: Den Delimarsky <hi@den.dev>
Co-authored-by: Den Delimarsky <hi@den.dev>
Co-authored-by: Den Delimarsky <hi@den.dev>
Co-authored-by: Den Delimarsky <hi@den.dev>
…/modelcontextprotocol into add-server-instructions
Co-authored-by: Den Delimarsky <hi@den.dev>
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.
I was originally going to post a personal blog and make some tweaks to docs related to Server Instructions, but thought it could be better to add an official blog post as a followup from the Prompts post.
Some of this could go into other parts of the documentation instead. Sharing what I have so far here to get feedback and suggestions.
Motivation and Context
More clients are starting to add support for this feature, and it relates to a lot of use cases I've seen discussed. A few of them are here, but its not totally exhaustive.
How Has This Been Tested?
N/A
Breaking Changes
N/A
Types of changes
Checklist
Additional context
VSCode is going to release this feature soon, so @dend maybe something like this could be coordinated for when that release happens? (I believe its only in Insiders so far?)