Overview
The Neostella Model Context Protocol (MCP) Server enables external AI tools, including Microsoft 365 Copilot, to securely authenticate and access Neostella platform data. Configuring this integration extends Neostella data to Microsoft 365 Copilot in real time while preserving the existing granular security model of the platform. This eliminates manual data exports and reduces administrative overhead.
Integration Scope
This integration establishes a connection between Microsoft 365 Copilot and the Neostella MCP Server endpoint (https://api.neostella.app/v1/mcp/server).
- Real-Time Federated Access: Data remains within the Neostella environment and is retrieved in real time rather than being duplicated.
- Permission Enforcement: Available tools and accessible records are strictly governed by the object-level permissions assigned to the authenticated user in Neostella.
Requirements
Dependencies
- Feature Flag: The MCP functionality is controlled via a Feature Flag. Although the configuration steps can be completed in advance, the MCP Server cannot be accessed until the feature is enabled by the Neostella Admin.
Prerequisites
- Microsoft 365 Role: AI Administrator role in Microsoft 365.
- Microsoft 365 License: Active Microsoft 365 Copilot license.
- Neostella Access: A Neostella user account with MCP access to complete the initial connection test and authorization.
Required Permissions
- Users must be assigned to the Workspace - AI MCP permission set in Neostella.
- Access to the MCP Server is blocked by default.
Limitations
- Object-Level Restrictions: The MCP Server respects user-granted permissions. Users cannot read records via the MCPServer if those users do not have access to the records in Neostella.
- Teams App Restriction: In the Microsoft Teams Developer Portal, the Restrict usage by Teams app setting must be configured to Any Teams app (for testing and store validation only) for production deployments.
Authentication
Authentication between Microsoft 365 Copilot and the Neostella MCP Server uses OAuth 2.0 with Proof Key for Code Exchange (PKCE) enabled.
- Client ID: 6echh79f8kkgett0jmh5225vbo
- Client Secret: 6echh79f8kkgett0jmh5225vbo (identical to the Client ID)
- Authorization Endpoint: https://neostella.app/auth/mcp-login
- Token Endpoint: https://api.neostella.app/v1/mcp/token
- Client Password Authentication Method: HTTP Basic authentication
- User-Level Authentication: The initial authorization performed during connector setup validates the connection from Microsoft. Individual end users must authenticate with their own Neostella credentials to access platform data through Microsoft 365 Copilot.
Data Flow
- A user submits a query in Microsoft 365 Copilot.
- Microsoft 365 Copilot sends an authenticated request to the Neostella MCP Server (https://api.neostella.app/v1/mcp/server) using the OAuth 2.0 token of the user.
- The Neostella MCP Server verifies that the Feature Flag is enabled and checks the Workspace - AI MCP permission set and object-level permissions assigned to the user.
- The Neostella MCP Server retrieves the authorized data in real time and returns the results to Microsoft 365 Copilot.
Configuration Steps
Step 1: Configure User Permissions in Neostella
Assign users to the Workspace - AI MCP permission set to grant access to the MCP Server.
- Open Control Center.
- Open Access, and select Permissions.
- Select the Filter option, choose Type under Columns, select the contains operator, and enter mcp in the Value field.
- Select the Workspace - AI MCP permission set. If the permission set does not exist, click + NEW PERMISSION SET, set the Type to Workspace - AI MCP, and enter a descriptive Name such as MCP Server Access.
- Add the users who require access to the MCP Server under the ASSIGNEES tab.
- Click SAVE.
Step 2: Create an OAuth Client Registration
Register the Neostella OAuth client in the Microsoft Teams Developer Portal to generate the Reference ID required by Microsoft 365.
- Navigate to https://dev.teams.microsoft.com/.
- Select Tools in the left navigation menu, and click OAuth client registration.
- Click New OAuth client registration.
- Complete the App settings and OAuth settings fields with the following values:
| Field | Value |
| Registration name | Neostella |
| Base URL | https://api.neostella.app |
| Restrict usage by organization | My organization only |
| Restrict usage by Teams app | Any Teams app |
| Client ID | 6echh79f8kkgett0jmh5225vbo |
| Client secret | 6echh79f8kkgett0jmh5225vbo |
| Authorization endpoint | https://neostella.app/auth/mcp-login |
| Token endpoint | https://api.neostella.app/v1/mcp/token |
| Refresh endpoint | Leave blank |
| Scope | Leave blank |
| Enable Proof Key for Code Exchange (PKCE) | True |
| Client password authentication method | HTTP Basic authentication |
- Click Save.
- Copy the generated OAuth client registration ID for use in the next procedure.
Step 3: Configure the Connector in Microsoft 365 admin center
Create the custom MCP connector in Microsoft 365 admin center to make the integration available to users.
- Open Microsoft 365 admin center.
- Navigate to Copilot > Connectors.
- Click + Add Connection.
- Locate Create a new connector under Created by your org, and click Add.
- Under Connect to MCP server, click Add.
- Complete the connector configuration fields with the following values:
| Field | Value |
| Display name | Neostella |
| Description | Neostella MCP Connector |
| MCP endpoint URL | https://api.neostella.app/v1/mcp/server |
| Developer name | Neostella |
| Website URL | https://neostella.com |
| Privacy policy URL | https://neostella.com/privacy |
| Terms of use URL | https://neostella.com/terms-of-use |
| Authentication type | OAuth 2.0 |
| Reference ID | Paste the OAuth client registration ID copied in Step 2 |
- Click Authorize to open a new browser tab for Neostella authentication.
- Log in using a Neostella account that has Workspace - AI MCP access. Once authenticated, the login window closes automatically and the connector setup displays an authorized status.
- Select the Notice checkbox to accept the terms.
- Click Create.
Validation
Verify that the connector is active and returning data as expected:
- In Microsoft 365 admin center, navigate to Copilot > Connectors > Your Connections.
- Confirm that Neostella appears in the list and that the State is Ready.
- Open a new chat in Microsoft 365 Copilot and add the Neostella connector.
- Request Microsoft 365 Copilot to search for a specific project that the authenticated user has permission to view in Neostella.
- Verify that Microsoft 365 Copilot returns the matching project details.
Troubleshooting
| Problem Description | Possible Cause | Resolution Steps |
| The server rejects the request after successful authentication. | The MCP Feature Flag is not enabled for the Admin. | Contact the Neostella Product team to verify the Feature Flag status and enable it for the Admin. |
| Microsoft 365 Copilot indicates no records are found, but records exist in Neostella. | The authenticated user does not have permission to view the records. | Review the permissions assigned to the user in Control Center to ensure the user has object-level access to the data. |
| The user cannot authenticate to the MCP Server. | The user is not added to the allow list. | Ensure the user is assigned to the Workspace - AI MCP permission set in Control Center. |