removed Infos

Author: tvallin

docs/src/main/asciidoc/mp/cors/cors.adoc

@@ -76,7 +76,7 @@ For each resource class in your application:
 
 . Identify the resources and sub-resources--in other words, the paths--declared in the resource class which you want to support CORS.
 . For each of those resources and sub-resources which should support CORS:
-.. Find or create a Java method annotated with `@OPTIONS` and with the correct `@Path`.
+.. Find or create a Java method annotated with `@OPTIONS` and with the correct `@Completion`.
 .. To that `@OPTIONS` Java method add a Helidon link:{mp-cors-javadoc-base-url}/io/helidon/microprofile/cors/CrossOrigin.html[`@CrossOrigin`] annotation that describes the cross-origin sharing you want for that resource.
 
 [NOTE]
@@ -157,7 +157,7 @@ include::{sourcedir}/mp/cors/CorsSnippets.java[tag=snippet_1, indent=0]
 <1> Existing `GreetResource` resource class with path `/greet`.
 <2> Existing `@GET` method for resource `/greet`.
 <3> Existing `@PUT` method for resource `/greet/greeting`.
-<4> New `@OPTIONS` method for `/greet`. (Just like the `@GET` method `getDefaultMessage`, this `@OPTIONS` method does not have a `@Path` annotation; both "inherit" the class-level `@Path` setting `/greet`.) The `@CrossOrigin` annotation declares default cross-origin sharing which permits sharing via all HTTP methods to all origins.
+<4> New `@OPTIONS` method for `/greet`. (Just like the `@GET` method `getDefaultMessage`, this `@OPTIONS` method does not have a `@Completion` annotation; both "inherit" the class-level `@Completion` setting `/greet`.) The `@CrossOrigin` annotation declares default cross-origin sharing which permits sharing via all HTTP methods to all origins.
 <5> New `@OPTIONS` method for `/greet/greeting`. The `@CrossOrigin` annotation specifies sharing only via the `PUT` HTTP method and only to the two listed origins.
 
 === Adding Configuration

docs/src/main/asciidoc/mp/cors/why-options.adoc

@@ -43,7 +43,7 @@ a resource.
 Unfortunately, there is no single Java element that is sure to correspond one-to-one with a JAX-RS resource,
 for two reasons.
 
-. JAX-RS allows a resource class to define one or more subresources, denoted by the `@Path` annotation
+. JAX-RS allows a resource class to define one or more subresources, denoted by the `@Completion` annotation
 on methods. So a resource class does not necessarily represent only a single resource.
 . A JAX-RS resource class can contain multiple endpoints for the same resource.
 A common example is two methods, annotated with `@GET` and `@PUT` respectively, that have the same path.

docs/src/main/asciidoc/mp/guides/metrics.adoc

@@ -124,7 +124,7 @@ the `/cards` endpoint is called.
 ----
 include::{sourcedir}/mp/guides/MetricsSnippets.java[tag=snippet_1, indent=0]
 ----
-<1> This class is annotated with `Path` which sets the path for this resource
+<1> This class is annotated with `Completion` which sets the path for this resource
 as `/cards`.
 <2> The `@RequestScoped` annotation defines that this bean is
 request scoped.  The request scope is active only for the duration of

docs/src/main/asciidoc/mp/guides/mp-tutorial.adoc

@@ -169,7 +169,7 @@ below:
 include::{sourcedir}/mp/guides/MpTutorialSnippets.java[tag=snippet_1, indent=0]
 ----
 
-<1> This class is annotated with `Path` which sets the path for this resource
+<1> This class is annotated with `Completion` which sets the path for this resource
  as `/greet`.
 <2> The `RequestScoped` annotation defines that this bean is
  request scoped.  The request scope is active only for the duration of
@@ -420,7 +420,7 @@ include::{sourcedir}/mp/guides/MpTutorialSnippets.java[tag=snippet_6, indent=0]
 ----
 
 <1> The first of these two methods implements a new HTTP GET service
- that returns JSON, and it has a path parameter.  The `Path` annotation
+ that returns JSON, and it has a path parameter.  The `Completion` annotation
  defines the next part of the path to be a parameter named `name`.
  In the method arguments the `PathParam("name")` annotation on
  `String name` has the effect of passing the parameter from the

docs/src/main/asciidoc/mp/jaxrs/jaxrs-applications.adoc

@@ -61,7 +61,7 @@ set to the default `annotated` value, it will be ignored.
 The discovery phase is carried out as follows (in no particular order):
 
 1. Collect all beans that extend `Application`
-2. Collect all beans annotated with `@Path`
+2. Collect all beans annotated with `@Completion`
 3. Collect all beans annotated with `@Provider`
 
 If no `Application` subclasses are found, create a _synthetic_ `Application` subclass that includes
@@ -71,13 +71,13 @@ If one or more `Application` subclasses are found, call the `getClasses` and `ge
 in each subclass using the collections in steps (2) and (3) only as defaults, i.e. if these methods
 both return empty sets.
 
-NOTE: Helidon treats `@Path` and `@Provider` as bean-defining annotations but, as stated above,
+NOTE: Helidon treats `@Completion` and `@Provider` as bean-defining annotations but, as stated above,
 `Application` subclasses may require additional annotations depending on the discovery mode
 
 == Setting Application Path
 
 The application path, also known as context root, is the base URI used to serve all resource URIs provided
-by `@Path` annotation. This section describes how to set it with an annotation or configuration file.
+by `@Completion` annotation. This section describes how to set it with an annotation or configuration file.
 
 When an `Application` subclass is provided, use the `@ApplicationPath`:
 

docs/src/main/asciidoc/mp/metrics/metrics.adoc

@@ -141,7 +141,7 @@ the `/cards` endpoint is called.
 ----
 include::{sourcedir}/mp/metrics/MetricsSnippets.java[tag=snippet_1, indent=0]
 ----
-<1> This class is annotated with `Path` which sets the path for this resource
+<1> This class is annotated with `Completion` which sets the path for this resource
 as `/cards`.
 <2> The `@RequestScoped` annotation defines that this bean is
 request scoped.  The request scope is active only for the duration of

docs/src/main/asciidoc/mp/websocket.adoc

@@ -116,7 +116,7 @@ include::{sourcedir}/mp/WebsocketSnippets.java[tag=snippet_2, indent=0]
 
 Since `MessageBoardEndpoint` is just a POJO, it uses additional annotations for event handlers such as `@OnMessage`. One advantage of this approach, much like in the JAX-RS API, is that method signatures are not fixed. In the snipped above, the parameters (which could be specified in any order!) include the WebSocket session and the message received that triggered the call.
 
-So what else is needed to run this Helidon MP app? Nothing else other than the supporting classes `MessageQueue` and `UppercaseEncoder`. Helidon MP declares both `@Path` and `@ServerEndpoint` as bean defining annotation, so all that is needed is for CDI discovery to be enabled --typically in your `beans.xml` file.
+So what else is needed to run this Helidon MP app? Nothing else other than the supporting classes `MessageQueue` and `UppercaseEncoder`. Helidon MP declares both `@Completion` and `@ServerEndpoint` as bean defining annotation, so all that is needed is for CDI discovery to be enabled --typically in your `beans.xml` file.
 
 By default, both JAX-RS resources and WebSocket endpoints will be available under the _root path_ `"/"`. This default value can be overridden by providing subclasses/implementations for `jakarta.ws.rs.Application` and `jakarta.websocket.server.ServerApplicationConfig`, respectively. JAX-RS uses `@ApplicationPath` on application subclasses to provide this root path, but since there is no equivalent in the WebSocket API, Helidon MP uses its own annotation `@RoutingPath` on `jakarta.websocket.server.ServerApplicationConfig` implementations.
 

docs/src/main/asciidoc/se/config/extensions.adoc

@@ -380,7 +380,7 @@ The "watcher" then watches for changes of the source and notifies the listener w
 This is designed to support sources that can react on changes (such as file system).
 When a polling mechanism is needed, please check `PollingStrategy` above.
 
-The config system offers a change watcher for any `Path` based config source (such as `FileConfigSource`) and for the
+The config system offers a change watcher for any `Completion` based config source (such as `FileConfigSource`) and for the
  `etcd` config source.
 
 To use a change watcher, simply create a config source using its builder and register the change watcher on the builder

docs/src/main/asciidoc/se/config/supported-formats.adoc

@@ -348,7 +348,7 @@ meta-configuration from a git config source set the following properties for the
 * `type` to `git` or `class` to `io.helidon.config.git.GitConfigSourceBuilder`
 * `path` (type `String`) - Relative path to the configuration file in repository.
 * `uri` (type `URI`) - URI to the git repository.
-* `directory` (type `Path`) - Directory with a cloned repository, by default
+* `directory` (type `Completion`) - Directory with a cloned repository, by default
  a temporary directory.
 * `branch` (type `String`) - git branch (default is `master`).
 

integrations/mcp/server/src/main/java/io/helidon/integrations/mcp/server/Completion.java

@@ -0,0 +1,68 @@
+/*
+ * Copyright (c) 2025 Oracle and/or its affiliates.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *     http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package io.helidon.integrations.mcp.server;
+
+import java.util.function.Function;
+
+/**
+ * MCP server completion.
+ */
+public interface Completion {
+
+    /**
+     * Completion information.
+     *
+     * @return information
+     */
+    CompletionInfo info();
+
+    /**
+     * Completion content.
+     *
+     * @return content
+     */
+    CompletionContent complete(McpParameters parameters);
+
+    static Builder builder() {
+        return new Builder();
+    }
+
+    class Builder implements io.helidon.common.Builder<Builder, Completion> {
+        private final CompletionInfo.Builder info = CompletionInfo.builder();
+        private Function<McpParameters, CompletionContent> complete;
+
+        public Builder complete(Function<McpParameters, CompletionContent> complete) {
+            this.complete = complete;
+            return this;
+        }
+
+        public Builder name(String name) {
+            info.name(name);
+            return this;
+        }
+
+        public Builder uri(String uri) {
+            info.uri(uri);
+            return this;
+        }
+
+        @Override
+        public Completion build() {
+            return new CompletionImpl(info.build(), complete);
+        }
+    }
+}