A Model Context Protocol (MCP) server that provides AI assistants with access to OpenSlice service management capabilities through standardized tools and resources.
## Overview
## Getting started
The OpenSlice MCP Server is a Spring Boot application that bridges OpenSlice's service catalog and management system with AI assistants like Claude via the Model Context Protocol. It exposes OpenSlice functionality as MCP tools, allowing AI assistants to interact with service catalogs, manage service orders, and retrieve service information.
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
## What is OpenSlice?
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
[OpenSlice](https://osl.etsi.org/) is an open-source platform for managing network services and resources based on TMForum standards. It provides service catalog management, service ordering, and service lifecycle management capabilities for telecommunications and cloud services.
## Add your files
## Features
-[ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-[ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
- Create service orders with customizable characteristics
- Track service order status and progress
- Retrieve service order details and history
## Integrate with your tools
-**Service Instance Management**:
- View service instances and their details
- Update service characteristics
- Monitor service status and supporting resources
-[ ] [Set up project integrations](https://labs.etsi.org/rep/osl/code/org.etsi.osl.mcp.server/-/settings/integrations)
-**Resource Management**:
- Access resource information and specifications
- Track resource status and characteristics
## Collaborate with your team
### Authentication & Security
-[ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-[ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-[ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- Secure communication with OpenSlice backend systems
## Test and Deploy
## Architecture
Use the built-in continuousintegration in GitLab.
The server implements the MCP protocol using Spring AI's MCP server capabilities:
-[ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/)
-[ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-[ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-[ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-[ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-**Transport**: Server-Sent Events (SSE) for real-time communication
-**Message Queue**: Apache ActiveMQ for backend communication with OpenSlice
-**Protocol**: Model Context Protocol v1.0 for AI assistant integration
***
## Configuration
# Editing this README
Key configuration options in `application.yaml`:
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
```yaml
server:
port:13015
## Suggestions for a good README
spring:
ai:
mcp:
server:
name:org.etsi.osl.mcp.server
sse-message-endpoint:/mcp/messages
stdio:false
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Installation & Usage
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
### Prerequisites
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
- Java 17 or higher
- Maven 3.6+
- Access to an OpenSlice deployment
- Access to the OpenSlice ActiveMQ message broker
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
### Building
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
```bash
mvn clean package
```
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
### Running
```bash
java -jar target/org.etsi.osl.mcp.server-*.jar
```
The server will start on port 13015 and provide MCP endpoints for AI assistant integration.
### Integration with Claude
Once running, the server can be connected to Claude Code or other MCP-compatible clients:
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
1. The server exposes its MCP interface at: `http://localhost:13015/mcp/messages`
2. AI assistants can discover and use the available tools for OpenSlice operations
3. Authentication is required via JWT tokens from the configured OAuth2 provider
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
for Claude:
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
```
{
"mcpServers": {
"oslserver": {
"command": "npx",
"args": [
"mcp-remote@latest",
"http://portal.openslice.eu:13015/sse",
"--allow-http"]
}
}
}
```
## Dependencies
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
- Spring Boot 3.4.5
- Spring AI with MCP server support
- Apache Camel for message routing
- TMForum API models for telecommunications standards
- ActiveMQ for message queue communication
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
This project is licensed under the Apache License 2.0.
## Related Projects
-[OpenSlice](https://osl.etsi.org/) - The main OpenSlice platform
-[Model Context Protocol](https://modelcontextprotocol.io/) - Protocol specification for AI assistant integrations
