Incorporate HTTP headers for OpenAPI spec #26
Description
Incorporate #3 (comment) (@connor4312).
Authorization would definitely be the most common. Even in a world where MCP auth is widely adopted, there'll always be some cases and servers who want to do basic API key types things for any variety of reasons. I've also seen some APIs that do versioning via X-Api-Version headers.
@sandy081 said:
Yes, it is similar to local package arguments. This is how we envisioned for example:
"remote": {
"type": "object",
"description": "Remote server configuration",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"format": "uri",
"description": "URL of the remote server"
},
"transport_type": {
"type": "string",
"description": "Transport type for the remote server",
"enum": [
"streamable",
"sse"
]
},
"headers": {
"type": "array",
"description": "Headers to be sent to the remote server",
"items": { "$ref": "#/definitions/argument" }
}
}
}
#/definitions/argumentis the schema for the argument that is also used for local package arguments.
Careful not to merge-conflict with #25
Metadata
Metadata
Assignees
Labels
No labels