Tangensys • Plan, deliver, measure
MCP server development
Expose a small, well-defined set of business tools to compatible AI clients. The protocol connection is only one part of authentication and permission design.
The work to plan together
A scope shaped around this requirement.
- Tool and data designScope
- Server buildReview
- AuthenticationCheck
- Be foundSearch, maps and AI answers
- Be chosenClear pages and offers
- EnquiryCall, WhatsApp or form
- Follow-upYour team responds
In short
What does MCP server development involve?
MCP server development builds Model Context Protocol servers that let AI assistants use your business data and tools securely.
When MCP server development is a useful fit
SaaS companies
Expose a small, clearly defined set of documented tools with clear authentication and permissions.
Teams using AI assistants internally
Check which records an assistant may access and which actions require human approval.
Problems worth addressing first
Use these situations to identify the work that deserves attention before expanding the scope.
- AI assistants cannot reach your systems
A practical example
An assistant may read an order status through a restricted tool while order changes use a separate action with explicit permission and logging.
This is an illustrative scenario to explain the approach, not a claimed client project.
The work we can include
The final quote identifies the deliverables, quantities, approvals and exclusions. Select the work that serves your goal rather than assuming every item is required.
- Tool and data design
- Server build
- Authentication
- Documentation
Where we usually begin
Client compatibility, authentication, hosting and tool boundaries are tested. MCP does not automatically make a tool safe or grant access to every system.
Practical detail
A small tool contract with explicit write authority
An illustrative MCP server exposes a read tool for order status. A separate change-address tool needs stronger validation and an agreed approval route.
| Part of the work | Example output | How to review it |
|---|---|---|
| Read tool | get_order_status with an order reference | Authentication and access checks restrict which order can be read. |
| Write tool | change_delivery_address with validated fields | The tool applies the permitted action and requires the agreed authorisation. |
| Response/error | Structured status or an actionable failure | The client can distinguish unavailable data from a completed update. |
| Interoperability record | Supported clients, authentication route and test cases | The actual client/server combination is tested rather than assumed compatible. |
MCP describes an interaction protocol; it does not remove the need for secure application rules. Tool schemas, access checks and logging follow current protocol documentation and the specific deployment.
Expose only the tools a supported client should use
An MCP server can make selected resources or tools available to a compatible client. The design should begin with the intended consumer, authentication boundary and task. Exposing every internal endpoint is neither necessary nor a complete integration plan.
Describe tool inputs, outputs and side effects. Reading a status and changing a record need different review and permissions. Current client and protocol capabilities should be checked against official documentation during technical discovery.
Test valid calls, denied access, invalid input and the agreed failure path. Keep setup, version dependencies and operator notes in the handover. A compatible tool description does not replace application-level permission checks.
Free AI project review
Start with a clear scope and a practical next step.
Tell us what you want to improve and share the relevant website or project details. We will review the starting point, recommend a suitable scope and provide a custom quote.
The initial review is free. Delivery, third-party charges and ongoing support are quoted separately.
Process
How the work is delivered
Review the starting point
Review the current setup, examples of the problem and the information needed to agree the work.
Agree scope and sign-off
We start with real examples of the task and approved information. A small, clearly defined pilot tests usefulness, failure cases and the level of human oversight before wider rollout.
Deliver and review
Evaluation includes inaccurate answers, unavailable tools and uncertain requests. Provider charges, monitoring and updates are defined separately; the business keeps an accountable human owner.
Hand over the next steps
Review the agreed outputs together. Confirm what your team maintains and what needs a separate ongoing arrangement.
What progress should mean
Measures that match the work
Verify tool behaviour, access isolation, useful errors and compatibility with the agreed clients. Document inputs, outputs and operational responsibilities.
A record of delivery
See what was completed, reviewed and still dependent on access or approvals. Project delivery and business results are reported separately.
Clear limits in the data
We explain what can be verified and where a result is only an estimate. Contact clicks, conversations and sales are different actions.
Scope and responsibilities
You keep ownership of your business accounts and approved deliverables under the agreed contract. Any third-party licences, subscriptions or usage fees are identified before you commit.
What belongs in an MCP discovery brief?
Name the client, approved resources, required actions and identity model. Include examples of permitted and denied tasks. The technical team can then assess implementation, testing and maintenance instead of estimating from a generic request to connect an AI tool.
Does exposing a tool mean an assistant may always use it?
No. Availability, permissions, client behaviour and the business’s approval policy all matter.
Will a server work with every MCP client?
Do not assume it. Agree supported clients and protocol features, then record interoperability checks for those combinations.
What is MCP?
An open protocol for connecting AI assistants to tools and data.
How is MCP server development priced?
We quote against your goals, current setup and agreed scope. The quote separates delivery from third-party costs and ongoing support. You receive a custom quote within 2 working days.
How long does the work take?
The timeline follows the size of the agreed scope, access, content and approvals. We confirm milestones in the quote; a simple change and a full implementation need different schedules.
How will we communicate?
Your point of contact agrees a review rhythm with you. We use email, WhatsApp and scheduled calls, with decisions and scope changes recorded clearly.
What do you need to get started?
Share your current website or system, your main goal and examples of what is not working. We then agree the access and information needed for discovery.
Is everything included in the free review?
No. The free initial review helps define the next step. Detailed research, design, implementation and ongoing support are included only when stated in your quote.
Explore the related services
Let’s agree the right next step.
Tell us your goals and current setup. We’ll recommend a practical starting point and provide a custom quote.
Custom quote within 2 working days